El martes, 2 de julio de 2019, 18:44:39 (UTC+2), Nalin Garg escribió:
>
> I had a similar need. I ended up querying git to give list of all files
> that were changed in PR. And then have logic around what files would be
> wrapped in "if, else"/ "when" block.
>
>
I preffer to use `when` at s
Hi
If you have a free-style job, you could convert it to pipeline job, so that
you can use leverage using conditional flows in it.
On Tuesday, July 2, 2019 at 7:18:23 PM UTC+5:30, Vijay Gongle wrote:
>
> I have a Jenkins pipeline which has 10 Jobs configured to run one after
> the other in the p
I had a similar need. I ended up querying git to give list of all files
that were changed in PR. And then have logic around what files would be
wrapped in "if, else"/ "when" block.
On Tuesday, July 2, 2019 at 6:48:23 AM UTC-7, Vijay Gongle wrote:
>
> I have a Jenkins pipeline which has 10 Jobs
One technique is to create a single Jenkins Pipeline job that performs all
10 of those steps, then use the declarative Pipeline ability to
conditionally skip a step based on conditions you decide.
However, I've never tried to manage that complex a Pipeline job, so I can't
comment more than to sugg
I have a Jenkins pipeline which has 10 Jobs configured to run one after the
other in the post build action.
Anytime there's a change in Job's related git code, the build is triggered
and all the following jobs run though rest of the Job code were not
committed.
For e.g, in a series of 10 jobs
