www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Meghna Baijal <meghnabaijal2...@gmail.com>
Subject Re: (MXNet) Testing changes to the Jenkinsfile without merging to the repo.
Date Tue, 19 Sep 2017 21:12:10 GMT
Thanks Joan. That helps! 

Meghna Baijal
> On Sep 19, 2017, at 2:02 PM, Joan Touzet <wohali@apache.org> wrote:
> Multibranch pipeline builds always use the Jenkinsfile in a specific branch
> when testing that branch. So, your changes to the Jenkinsfile pre-merge will
> only affect builds on that branch. Hopefully this is enough?
> You can always create a new multibranch pipeline build that has a filter on
> which branches it will build on, and have that job use the new Jenkinsfile.
> You can then test it out on any branch prefixed with jenkins- (for example).
> -Joan
> ----- Original Message -----
> From: "Meghna Baijal" <meghnabaijal2017@gmail.com>
> To: builds@apache.org
> Sent: Tuesday, 19 September, 2017 4:45:51 PM
> Subject: (MXNet) Testing changes to the Jenkinsfile without merging to the repo.
> 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
> 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
> 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

View raw message