--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0jXNj9-XCTWXERUQz%2B7Vx9sVrPor%2BraJU-GSHvaoMsWw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Yes declarative has both of these in a way via the when directive's branch and changeset conditions. If I've interpreted forBranch and forChangesIn correctly :)
2018-04-11 23:39 GMT+02:00 Jesse Glick <jgl...@cloudbees.com>:
Declarative Pipeline certainly can easily do the same as `forBranch`,
and from Scripted you can trivially write the same thing, so I think
no new step is warranted.
Not quite sure I follow what `forChangesIn` is about, but sounds like
a candidate for a new plugin.
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0jXNj9-XCTWXERUQz%2B7Vx9sVrPor%2BraJU-GSHvaoMsWw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/mDLg7W6Xq68/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr051Mhd8PtLfdbDzq5GFZbGFMgqwVQFAZ4CCrh88%3D%3D6tA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful.