matlab-2.2.0

Bug Fixes

• Fix for the invalid MATLAB root issue in freestyle and multi-configuration projects.
  If you specify an invalid MATLAB version in the Build Environment section of the project configuration window, the plugin fails your build for that version. In previous releases, the plugin tries to run the build by replacing the invalid MATLAB version with the version of the first MATLAB executable it encounters on the system path.

Compatibility Considerations

• When you use the Run MATLAB Tests build step, the plugin generates a randomly named MATLAB script file and uses it to run the tests and produce the test artifacts. The plugin deletes the file once the build is complete. You can view the contents of the file in the build log.
  In previous releases, the Run MATLAB Tests build step generates a file named runMatlabTests.m, which the plugin stores in the project workspace and does not delete. Because this file is no longer useful, consider removing it from your workspace.

matlab-2.1.3

Bug Fixes

• Fix for the test artifact selection issue.
  If you specify artifacts and file paths in the Run MATLAB Tests build step, your settings persist when Jenkins restarts.

matlab-2.1.2

Bug Fixes

• Fix for the build step timeout issue.
  The runMATLABCommand and runMATLABTests steps adhere to the time limit specified using a timeout block.

matlab-2.1.1

Bug Fixes

• Fix for the MATLAB startup issue.
  If the project workspace contains a startup.m file, the plugin executes the user-specified commands within the file when starting MATLAB.

matlab-2.1.0

Features

• Use runMATLABCommand and runMATLABTests to run MATLAB code and Simulink models with declarative and scripted pipelines.
  For more information, see Plugin Configuration Guide.

Compatibility Considerations

• When you specify MATLAB commands (either in the Run MATLAB Command section of the web UI or in the runMATLABCommand step of your Jenkinsfile), the plugin writes your commands to a UTF-8 encoded file and invokes the generated script instead. In previous releases, the plugin directly runs the specified commands.
  Due to this behavior change, MATLAB might display non-ASCII characters, specified in your commands, as garbled text. If you specify non-ASCII characters in your commands, consider running your commands as a .m or .mlx file created in the same locale that MATLAB uses on the build agent.

matlab-2.0.1

Features

• Generate test artifacts with custom names and locations.
  For more information, see Plugin Configuration Guide.

Compatibility Considerations

• When you generate a test artifact, you can customize the artifact name and location in the project configuration window. In previous releases, the plugin assigns a default name to the artifact and stores it in the matlabTestArtifacts folder of the project workspace.
  If you have a project that is configured using a previous release, your build still runs and artifacts are generated and stored in the matlabTestArtifacts folder. You can view or override the default values in the project configuration window.

• The auto-generated runMatlabTests script no longer accepts as input a logical value per supported artifact. Instead, the script accepts only a file path per selected artifact.

matlab-2.0.0

Features

• New Build Environment section for accepting the MATLAB root
• New MATLAB command construction script
• Support to use the default MATLAB root in the PATH variable if MATLAB root is not specified in the Build Environment section
• Support for two separate build steps:
  • Run MATLAB Tests
  • Run MATLAB Command
• Fix for issue 68
• Fix for issue 71

Compatibility Considerations

• You can configure the plugin using separate, well-defined steps. In previous releases, you can specify the MATLAB root folder, the test mode, and the desired test artifacts with a single build step.
  Update your projects using these options in the project configuration window:
  • To specify the MATLAB root folder, select the Use MATLAB version checkbox in the Build Environment section. Then, insert the root folder path in the MATALB root box.
  • To run tests automatically and generate test artifacts, use the Run MATLAB Tests build step in the Build section.
  • To run MATLAB commands, scripts, or functions, use the Run MATLAB Command build step in the Build section.
    For more information, see Plugin Configuration Guide.

matlab-1.1.2

Features

• Generate PDF test reports
• New example on how to configure the plugin
• Fix for an empty plugin issue

Known Issue

• Producing a PDF test report is not currently supported on macOS platforms.

matlab-1.1.1

Features

• Migration of documentation from Jenkins Wiki to GitHub
• Fix for MATLAB root help icon issue

matlab-1.1.0

Features

• Jenkins (master/agent) support for running MATLAB on remote agents
• Generate Simulink Test artifacts:
  • Cobertura model coverage report
  • Simulink Test Manager results
• Fix for the eval issue