[JIRA] (JENKINS-51936) Reduce trigger-happy building from master/upstream commits
Title: Message Title Mark Waite commented on JENKINS-51936 Re: Reduce trigger-happy building from master/upstream commits trejkaz I'm not aware of any user interface setting that will cause "Build now" to perform a merge with the master branch without also causing each change to the master branch to run the build. I suspect that use case might be possible to cover by creating a new plugin which adds that behavior as a branch discovery implementation. That is how the multibranch Pipeline implementation has been generally guiding implementations of specialized behaviors. You might also be able to implement the merge in your Jenkinsfile as a call to the git command line to perform the merge. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51936) Reduce trigger-happy building from master/upstream commits
Title: Message Title trejkaz commented on JENKINS-51936 Re: Reduce trigger-happy building from master/upstream commits After discussing this one with team members and others, I can confirm that we do still want to merge with the latest master if someone manually requests a new build, but that we still don't want new builds to kick off automatically for every change on master. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
