-
New Feature
-
Resolution: Fixed
-
Minor
-
None
Use-case:
The Apache Maven Jenkinsfile wants to run integration tests when testing a build of Maven core.
As new features are added, there is often a need to add associated integration tests.
It would be great if the Jenkinsfile could easily determine if there is a matching branch in the maven-integration-testing repository and check that out... but if there is no matching branch then the master branch should be used instead.
Something like
def tests=resolveScm(source:git(url:'https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git'), targets:[env.BRANCH_NAME,'master'])) node('ubuntu') { stage 'Checkout'{ ... checkout scm } ... } stage 'Integration Test' parallel linuxJava7:{ node('ubuntu') { checkout tests ... } },linuxJava8: { node('ubuntu') { checkout tests ... } },winJava7: { node('windows-2012') { checkout tests ... } },winJava8: { node('windows-2012') { checkout tests ... } } ...
There are a couple of important features:
- We want to use the SCMSource to create the SCM so that it has a pinned revision and the same version of the tests are used on each of the parallel integration test runs
- We want to allow a list of branches to be tried in preference order
- We want to avoid requiring conditional behaviour to use this feature in the pipeline so that it can also be used from pipeline-model-definition based pipelines
- relates to
-
-
- Open
-
- links to
[JENKINS-40906] Resolve an SCM from an SCMSource and a list of candidate target branch names
| Link | New: This issue relates to JENKINS-32018 [ JENKINS-32018 ] |
| Description |
Original:
Use-case: The [Apache Maven Jenkinsfile|https://github.com/apache/maven/blob/e51fc87277bb988aed7641d02fd888c77d0a1206/Jenkinsfile] wants to run integration tests when testing a build of Maven core. As new features are added, there is often a need to add associated integration tests. It would be great if the Jenkinsfile could easily determine if there is a matching branch in the maven-integration-testing repository and check that out... but if there is no matching branch then the master branch should be used instead. Something like {code} def tests=resolveSCM(source:git(url:'https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git'), targets:[env.BRANCH_NAME,'master'])) node('ubuntu') { stage 'Checkout'{ ... checkout scm } ... } stage 'Integration Test' parallel linuxJava7:{ node('ubuntu') { checkout tests ... } },linuxJava8: { node('ubuntu') { checkout tests ... } },winJava7: { node('windows-2012') { checkout tests ... } },winJava8: { node('windows-2012') { checkout tests ... } } ... {code} There are a couple of important features: # We want to use the {{SCMSource}} to create the {{SCM}} so that it has a pinned revision and the same version of the tests are used on each of the parallel integration test runs # We want to allow a list of branches to be tried in preference order # We want to avoid requiring conditional behaviour to use this feature in the pipeline so that it can also be used from pipeline-model-definition based pipelines |
New:
Use-case: The [Apache Maven Jenkinsfile|https://github.com/apache/maven/blob/e51fc87277bb988aed7641d02fd888c77d0a1206/Jenkinsfile] wants to run integration tests when testing a build of Maven core. As new features are added, there is often a need to add associated integration tests. It would be great if the Jenkinsfile could easily determine if there is a matching branch in the maven-integration-testing repository and check that out... but if there is no matching branch then the master branch should be used instead. Something like {code} def tests=resolveScm(source:git(url:'https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git'), targets:[env.BRANCH_NAME,'master'])) node('ubuntu') { stage 'Checkout'{ ... checkout scm } ... } stage 'Integration Test' parallel linuxJava7:{ node('ubuntu') { checkout tests ... } },linuxJava8: { node('ubuntu') { checkout tests ... } },winJava7: { node('windows-2012') { checkout tests ... } },winJava8: { node('windows-2012') { checkout tests ... } } ... {code} There are a couple of important features: # We want to use the {{SCMSource}} to create the {{SCM}} so that it has a pinned revision and the same version of the tests are used on each of the parallel integration test runs # We want to allow a list of branches to be tried in preference order # We want to avoid requiring conditional behaviour to use this feature in the pipeline so that it can also be used from pipeline-model-definition based pipelines |
| Remote Link | New: This issue links to "PR#46 (Web Link)" [ 15223 ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Code changed in jenkins
User: Stephen Connolly
Path:
pom.xml
src/main/java/org/jenkinsci/plugins/workflow/multibranch/ResolveScmStep.java
src/test/java/org/jenkinsci/plugins/workflow/multibranch/ResolveScmStepTest.java
http://jenkins-ci.org/commit/workflow-multibranch-plugin/ac4f279c4f5765e3d704c8c224fe2540f4cf5c51
Log:
[FIXED JENKINS-40906] Resolve an SCM from an SCMSource and a list of candidate target branch names
Code changed in jenkins
User: Stephen Connolly
Path:
src/main/java/org/jenkinsci/plugins/workflow/multibranch/ResolveScmStep.java
src/main/resources/org/jenkinsci/plugins/workflow/multibranch/ResolveScmStep/config.jelly
src/main/resources/org/jenkinsci/plugins/workflow/multibranch/ResolveScmStep/help-ignoreErrors.html
src/main/resources/org/jenkinsci/plugins/workflow/multibranch/ResolveScmStep/help-source.html
src/main/resources/org/jenkinsci/plugins/workflow/multibranch/ResolveScmStep/help-targets.html
src/main/resources/org/jenkinsci/plugins/workflow/multibranch/ResolveScmStep/help.html
http://jenkins-ci.org/commit/workflow-multibranch-plugin/c818d7dec11e20904a1ffd42631aaf2cd1c2218a
Log:
JENKINS-40906 The missing configuration UI
Code changed in jenkins
User: Stephen Connolly
Path:
pom.xml
src/main/java/org/jenkinsci/plugins/workflow/multibranch/ResolveScmStep.java
http://jenkins-ci.org/commit/workflow-multibranch-plugin/76f9cfa355b0840678433ddd8fb0a282040959a8
Log:
JENKINS-40906 I think this addresses the remaining code review comments
Some similarities and partial overlap in use-cases