Thanks for your feedbacks! So in the end, what is the solution you adopted? more coarse grained stages?
Le dimanche 24 juillet 2016 14:18:18 UTC+2, [email protected] a écrit : > > Hello Victor, > > I am faced with a similar problem and gave up on the idea rather early on. > Here are some of the characteristics of multiple stages of a pipeline > > - Ability of each stage to be explictly invoked by some command > - Ability of each stage to be re-run in such a way that it can start > off from where the previous stage finished > > The maven lifecycle reactor does not play well with these concepts. For > example, there is no elegant way to tell maven to compile the code assuming > that the generation phase has happened. Likewise, one cannot ask maven to > simply execute the tests assuming that compilation has already taken place. > The short answer that the benefits of breaking something into various > pipeline stages is lost when maven. > > The situation with gradle is not better as far as the relationship with > the build tool and jenkins is concerned. However, the fact that gradle is > much better at quickly checking if earlier steps have been completed makes > it only marginally better. > > > On Saturday, July 23, 2016 at 1:10:08 PM UTC+5:30, Victor Noël wrote: >> >> Hi, >> >> I'm trying to wrap wy head around moving to pipeline jobs. >> >> Currently I use maven jobs (but my question applies to freestyle jobs >> that execute maven) by executing one single build command that will >> validate constraints (checkstyle and/or other stuffs like that), generate >> code, compile, run test, run it test and deploy artefacts. >> >> What is the best way to convert to pipeline with multiple stages? >> >> My main concern is that if I simply run each of the step with maven in >> each stage, then I feel like some of steps from maven may be executed >> multiple times (such as test being executed again for it tests or for >> deploy). >> >> Is there some success stories around here on how to handle such a >> migration? >> >> Thanks! >> > -- 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/e869c7c4-2ea5-4d8b-8268-7a083348b2b7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
