Hi, To run checkstyle alone you can simply call mvn checkstyle:check ? If you really like to run that into a separate pipeline step...
The question is what kind of advantage you would expect by running generating code alone and afterwards in a different pipeline step to compile the generated code and another pipeline step to run the unit tests etc. instead of simply running: mvn deploy ? in a single step? What is the real advantage of this approach? Kind regards Karl Heinz Marbaise On Saturday, July 23, 2016 at 9:40:08 AM UTC+2, 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/8c5e6772-a197-40f0-a444-e8d59c7b13eb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
