-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid adding a PipelineTriggersJobProperty unless some triggers were actually configured #42
Avoid adding a PipelineTriggersJobProperty unless some triggers were actually configured #42
Conversation
[FIXES JENKINS-42446]
…actually configured.
configRoundtrip is no longer adding an empty property, so it has no effect on reproducibility of the bug.
IIRC the actual patch here is independent of #41, but it cannot be sanely tested without that. |
This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-approving. =)
Incorporates #41, without which
triggerPresentDuringStart
would fail, though I do not think that is mergeable as written.The idea of this PR is to ensure that in Pipeline Syntax for
properties
, if you do not select any triggers you will see justand not
@reviewbybees esp. @abayer