FWIW, you should really consider moving to Pipeline if you want to use something used by others where you have far bigger chance of feedback. Build Flow is deprecated.
My 2 cents 2017-02-24 8:21 GMT+01:00 Tomasz Szandała <[email protected]>: > Greetings All, > I am trying to go from build flow to Pipeline(and Jenkins2.x), but I have > encountered an issue: > I have complicated workflow, that should cause deploy. But deploy > requirements are fluent. Let's say I have something like this: > > I need all green ones to be requirements, but yellow ones to be perfomed, > but not mandatory success full in order to start blue one. > I was thinking about: each job editting some kind of map ["jobA": > "SUCCESS", "jobB": "FAILURE"] or in properties file. But how can I ensure > concurrency? > > Kind regards, > Tomasz > > P.S. > Keep in mind that requirements can change, so try / catch are too static. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-users/5964a845-594e-4cd0-8b88-fac2980186e9%40googlegroups. > com > <https://groups.google.com/d/msgid/jenkinsci-users/5964a845-594e-4cd0-8b88-fac2980186e9%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6hsjm2yyq9HO-VcT9LK8jN29VX8GNBQoGT8bzD5Z%2BTUw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
