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 :)
https://jenkins.io/doc/book/pipeline/syntax/#when /B 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-dev+unsubscr...@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. > -- *Robert Sandell* Software Engineer CloudBees, Inc. [image: CloudBees-Logo.png] <http://www.cloudbees.com/> E: rsand...@cloudbees.com Twitter: robert_sandell -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS0U0Sq6CbJjm4PksVtcP2XfCUBgjMqXSd5yc7Q-fGZakQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
