From 2de4b19cd8d129742cae2ad40bc6541f42dd9b7e Mon Sep 17 00:00:00 2001 From: nbhoski Date: Mon, 6 May 2019 16:49:54 +0530 Subject: [PATCH 1/5] Added note about SCM configuration for Automatic option. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c927f451..b7cc8571 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ Enter the value returned by “matlabroot” in the field named “MATLAB root ![new_enter_matlabroot](https://user-images.githubusercontent.com/47204011/55624374-45097e00-57c3-11e9-96e1-5fa0fc966767.png) #### Configuring “Automatic” Option -This option finds tests written using the MATLAB unit testing framework and/or Simulink Test and runs them. If the code is organized using projects, it will locate all test files in the project that have been classified as "Test". If the code does not leverage projects or uses a MATLAB version prior to R2019a, the plugin will discover all tests in the current Jenkins workspace including subfolders. +This option finds tests written using the MATLAB unit testing framework and/or Simulink Test and runs them. If the code is organized using projects, it will locate all test files in the project that have been classified as "Test". If the code does not leverage projects or uses a MATLAB version prior to R2019a, the plugin will discover all tests in the current Jenkins workspace including subfolders. When using "Automatic" option, It is mandatory for user to make sure that, appropriate SCM configuration is done before build step execution, which pulls the latest code from SCM into the Jenkins workspace. If SCM is not used to maintain the code then, user should make sure to add appropriate script, as part of build step before MATLAB plugin to copy the code in Jenkins workspace. The automatic test running feature enables you to generate different types of test artifacts. They could be used with other Jenkins plugins as part of a post-build action to publish the test results. To configure the Jenkins build for running MATLAB tests automatically, follow these steps. From 307a81eb1f6a9e8f2fa3bc14a523fdf08a19e5d7 Mon Sep 17 00:00:00 2001 From: nbhoski Date: Tue, 7 May 2019 11:51:50 +0530 Subject: [PATCH 2/5] Updated review comments #1 --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index b7cc8571..0d3bc57a 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,9 @@ Enter the value returned by “matlabroot” in the field named “MATLAB root ![new_enter_matlabroot](https://user-images.githubusercontent.com/47204011/55624374-45097e00-57c3-11e9-96e1-5fa0fc966767.png) #### Configuring “Automatic” Option -This option finds tests written using the MATLAB unit testing framework and/or Simulink Test and runs them. If the code is organized using projects, it will locate all test files in the project that have been classified as "Test". If the code does not leverage projects or uses a MATLAB version prior to R2019a, the plugin will discover all tests in the current Jenkins workspace including subfolders. When using "Automatic" option, It is mandatory for user to make sure that, appropriate SCM configuration is done before build step execution, which pulls the latest code from SCM into the Jenkins workspace. If SCM is not used to maintain the code then, user should make sure to add appropriate script, as part of build step before MATLAB plugin to copy the code in Jenkins workspace. +This option finds tests written using the MATLAB unit testing framework and/or Simulink Test and runs them. If the code is organized using projects, it will locate all test files in the project that have been classified as "Test". If the code does not leverage projects or uses a MATLAB version prior to R2019a, the plugin will discover all tests in the current Jenkins workspace including subfolders. + +If you are using source code management (SCM) system, like Git, then the job must include an appropriate SCM configuration to checkout the code before running the MATLAB plugin. If you are not using any SCM system to manage your code, then a previous build step should make sure the code is available in the workspace before running the MATLAB plugin. The automatic test running feature enables you to generate different types of test artifacts. They could be used with other Jenkins plugins as part of a post-build action to publish the test results. To configure the Jenkins build for running MATLAB tests automatically, follow these steps. From f14ff31de14e877dd3a2b1c560c9fd59cbcbc93f Mon Sep 17 00:00:00 2001 From: nbhoski Date: Wed, 8 May 2019 09:50:36 +0530 Subject: [PATCH 3/5] Updated review comments #2 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0d3bc57a..386733c6 100644 --- a/README.md +++ b/README.md @@ -20,7 +20,7 @@ Enter the value returned by “matlabroot” in the field named “MATLAB root #### Configuring “Automatic” Option This option finds tests written using the MATLAB unit testing framework and/or Simulink Test and runs them. If the code is organized using projects, it will locate all test files in the project that have been classified as "Test". If the code does not leverage projects or uses a MATLAB version prior to R2019a, the plugin will discover all tests in the current Jenkins workspace including subfolders. -If you are using source code management (SCM) system, like Git, then the job must include an appropriate SCM configuration to checkout the code before running the MATLAB plugin. If you are not using any SCM system to manage your code, then a previous build step should make sure the code is available in the workspace before running the MATLAB plugin. +If you are using a source code management (SCM) system such as Git, then the job must include an appropriate SCM configuration to check out the code before running the MATLAB plugin. If you do not use any SCM system to manage your code, then an additional build step is required to ensure the code is available in the workspace before running the MATLAB plugin. The automatic test running feature enables you to generate different types of test artifacts. They could be used with other Jenkins plugins as part of a post-build action to publish the test results. To configure the Jenkins build for running MATLAB tests automatically, follow these steps. From a46771f160c6901b4a442447892c9eafb53081a4 Mon Sep 17 00:00:00 2001 From: nbhoski Date: Thu, 9 May 2019 13:42:16 +0530 Subject: [PATCH 4/5] Updated inedx file with Simulink to make it searchable with Simulink keyword --- README.md | 2 +- src/main/resources/index.jelly | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 386733c6..aa2b6866 100644 --- a/README.md +++ b/README.md @@ -20,7 +20,7 @@ Enter the value returned by “matlabroot” in the field named “MATLAB root #### Configuring “Automatic” Option This option finds tests written using the MATLAB unit testing framework and/or Simulink Test and runs them. If the code is organized using projects, it will locate all test files in the project that have been classified as "Test". If the code does not leverage projects or uses a MATLAB version prior to R2019a, the plugin will discover all tests in the current Jenkins workspace including subfolders. -If you are using a source code management (SCM) system such as Git, then the job must include an appropriate SCM configuration to check out the code before running the MATLAB plugin. If you do not use any SCM system to manage your code, then an additional build step is required to ensure the code is available in the workspace before running the MATLAB plugin. +If you are using a source code management (SCM) system such as Git, then the job must include an appropriate SCM configuration to check out the code before running the MATLAB plugin. If you do not use any SCM systems to manage your code, then an additional build step is required to ensure the code is available in the workspace before running the MATLAB plugin. The automatic test running feature enables you to generate different types of test artifacts. They could be used with other Jenkins plugins as part of a post-build action to publish the test results. To configure the Jenkins build for running MATLAB tests automatically, follow these steps. diff --git a/src/main/resources/index.jelly b/src/main/resources/index.jelly index b41faa92..f33cabd7 100644 --- a/src/main/resources/index.jelly +++ b/src/main/resources/index.jelly @@ -1,5 +1,5 @@ - +
- Jenkins plugin to run MATLAB tests. + This plugin integrates MATLAB (R) with Jenkins and provides Jenkins interface to run MATLAB & Simulink (R) tests.
From da32f8f40f29b13836137ff97cbe585ca5f8ca50 Mon Sep 17 00:00:00 2001 From: nbhoski Date: Thu, 9 May 2019 14:22:09 +0530 Subject: [PATCH 5/5] Removed special character to fix test failure --- src/main/resources/index.jelly | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/resources/index.jelly b/src/main/resources/index.jelly index f33cabd7..2674dbf2 100644 --- a/src/main/resources/index.jelly +++ b/src/main/resources/index.jelly @@ -1,5 +1,5 @@
- This plugin integrates MATLAB (R) with Jenkins and provides Jenkins interface to run MATLAB & Simulink (R) tests. + This plugin integrates MATLAB (R) with Jenkins and provides Jenkins interface to run MATLAB and Simulink (R) tests.