Skip to content
This repository was archived by the owner on Mar 27, 2025. It is now read-only.

Commit a28575f

Browse files
authored
Update CONFIGDOC.md
1 parent 9e8a8c3 commit a28575f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

CONFIGDOC.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ You can use the Jenkins™ plugin for MATLAB® in freestyle and multi-con
1010
When you set up the Build **section** of the project configuration window, the plugin provides you with the **Run MATLAB Tests** and **Run MATLAB Command** build steps.
1111

1212
### Run MATLAB Tests
13-
This build step uses a default setting to run tests written using the MATLAB Unit Testing Framework and/or Simulink Test. If your source code is organized as files and folders within a MATLAB project, then the plugin includes any test files in the project that have been labeled as **Test**. If your code does not leverage a project or uses a MATLAB release before R2019a, the plugin includes all tests in the current Jenkins workspace including its subfolders.
13+
This build step uses a default setting to run tests written using the MATLAB Unit Testing Framework and/or Simulink® Test™. If your source code is organized as files and folders within a MATLAB project, then the plugin includes any test files in the project that have been labeled as **Test**. If your code does not leverage a project or uses a MATLAB release before R2019a, the plugin includes all tests in the current Jenkins workspace including its subfolders.
1414

1515
If you use a source code management (SCM) system such as Git™, then your project must include the appropriate SCM configuration to check out the code before it can invoke the MATLAB plugin. If you do not use any SCM systems to manage your code, then an additional build step is required to ensure that the code is available in the Jenkins workspace before the build starts.
1616

0 commit comments

Comments
 (0)