You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 27, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: CONFIGDOC.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,7 +109,7 @@ There are two ways to specify multiple MATLAB versions in a multi-configuration
109
109
### Add MATLAB Axis
110
110
If your Jenkins instance includes MATLAB versions registered as a tool, then MATLAB appears as an option when you click **Add axis** in the **Configuration Matrix** section. By adding the MATLAB axis, you can select MATLAB versions and add them as axis values to your matrix configuration. The list includes all MATLAB versions that have been registered as a Jenkins tool. In this example, there are two MATLAB versions registered as a tool. In each build iteration, the plugin prepends one of the selected versions to the PATH environment variable and invokes it to run the build.
For more information about registering MATLAB as a tool, see [Register MATLAB as Jenkins Tool](#register-matlab-as-jenkins-tool).
115
115
@@ -126,7 +126,7 @@ Note that a multi-configuration project creates a separate workspace for each us
126
126
127
127
You can add several axes in the **Configuration Matrix** section. For example, add the MATLAB axis to specify MATLAB versions and the user-defined TEST_TAG axis to specify the test tags for a group of tests.
Once you have specified the axes, add the required build steps in the **Build** section:
132
132
@@ -147,11 +147,11 @@ When you define your Pipeline with a `Jenkinsfile`, the plugin provides you with
147
147
148
148
To configure the plugin for a Pipeline project:
149
149
1) Define your Pipeline in a `Jenkinsfile` in the root of your repository.
150
-
2) In the **Pipeline** section of the project configuration window, select `Pipeline script from SCM` from the **Definition** list.
150
+
2) In the **Pipeline** section of the project configuration window, select **Pipeline script from SCM** from the **Definition** list.
151
151
3) Select your source control system from the **SCM** list.
152
152
4) Paste your repository URL into the **Repository URL** box.
153
153
154
-
You also can define your Pipeline directly in the project configuration window. If you select `Pipeline script` from the **Definition** list, you can author your Pipeline code in the **Script** box. When you define your Pipeline this way, your Pipeline must include an additional stage to check out MATLAB code from source control.
154
+
You also can define your Pipeline directly in the project configuration window. If you select **Pipeline script** from the **Definition** list, you can author your Pipeline code in the **Script** box. When you define your Pipeline this way, your Pipeline must include an additional stage to check out MATLAB code from source control.
155
155
156
156
### Add MATLAB to System Path
157
157
When the plugin executes MATLAB related steps in your Pipeline, it uses the topmost MATLAB version on the system path. If the PATH environment variable of the build agent does not include any MATLAB versions, you must update the variable with the MATLAB root folder that should be used for the build.
0 commit comments