Hi All,
I want to make some changes to the way PR builds are triggered on MXNet as
discussed in another email thread ("Run PR builds on Apache Jenkins only after
the commit is reviewed”)
Currently, there is a “Multibranch Pipeline" job in Jenkins that is responsible
for these MXNet builds. This job uses the jenkinsfile located in the source
code to build the project.
In order to make changes to the PR build triggers, I need to add some
properties to the Jenkinsfile script (as indicated here -
https://jenkins.io/doc/pipeline/steps/workflow-multibranch/#properties-set-job-properties
<https://jenkins.io/doc/pipeline/steps/workflow-multibranch/#properties-set-job-properties>)
My question is - How do I test these changes without merging them? Any untested
experiments with this jenkinsfile might lead to all the MXNet builds breaking.
Would it be ok to create a separate job in Apache Jenkins that points to a
private repo? Or is there a better way that I am unaware of?
Here is what I want to change and test -
1. Add a property to the Jenkinsfile so that if a new build is started for a
PR, any running or queued builds for the *same* PR are terminated.
2. Trigger PR builds based on comments in Github.
Any help or re-direction would be appreciated!
Thanks,
Meghna Baijal
