Re: [DISCUSS] Two new basic pipeline steps: forBranch() and forChangesIn()

> 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 :) Thanks Robert, this is exactly it (we are using scripted pipelines for their flexibility, I was not aware of this syntax in the

Re: [DISCUSS] Two new basic pipeline steps: forBranch() and forChangesIn()

On Fri, Apr 13, 2018 at 1:14 AM, wrote: > Is "when" also possible in scripted pipelines? You would just use `if` statements and the like. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from

Re: [DISCUSS] Two new basic pipeline steps: forBranch() and forChangesIn()

I think this will be a way to support those two features. Is "when" also possible in scripted pipelines? Am Donnerstag, 12. April 2018 11:13:28 UTC+2 schrieb Robert Sandell: > > Yes declarative has both of these in a way via the when directive's branch > and changeset conditions. If I've

Re: [DISCUSS] Two new basic pipeline steps: forBranch() and forChangesIn()

On Thu, Apr 12, 2018 at 5:13 AM, Robert Sandell wrote: > 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 `forChangesIn` sounded to me like something

Re: [DISCUSS] Two new basic pipeline steps: forBranch() and forChangesIn()

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 : > Declarative

Re: [DISCUSS] Two new basic pipeline steps: forBranch() and forChangesIn()

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

[DISCUSS] Two new basic pipeline steps: forBranch() and forChangesIn()

Hi all, we've been using the Jenkins pipelines pretty much from the day when they were released. As we use a fairly standardised build process across all projects in our organisation, we use shared libraries heavily to avoid redundancy across the repositories' Jenkinsfiles. For two little