So my plan for literate is to have a REST or socket exposed to the build which allows the maven build to notify the actions it undertook. Then by "cheating" slightly in how the mvn command launches, maven 3+ would have an extension that is an execution listener and would report back via the socket/REST end-point whether surefire ran, which modules did an install/deploy, which artifacts were attached to the reactor, etc. For Maven 2.x a maven plugin would be able to provide the same/similar by just adding the explicit goal up front. You would still be able to replicate the exact build behaviour from the command line in either case (as the command executed would be output in the log)
That "builder" would also be available to freestyle jobs. That is an approximate outline of my preferred way to get away from the evil job type. You would thus have the per-module breakdown, etc in freestyle and literate plugins On 11 September 2014 08:52, Nigel Magnay <[email protected]> wrote: > Would it be possible to create a 'jenkins maven plugin' that gives the > benefits of the maven job type, but with fewer of the disadvantages you > describe ? > > I.E: I'd be prepared to modify my builds to include a special CI plugin > (perhaps in a profile). We haven't actually had any problems with the maven > build type - but we need it because of stuff like declaring what artifacts > have been built (which is then consumed by the jenkins-maven-repository to > serve to downstream jobs). > > > > On Thu, Sep 11, 2014 at 8:29 AM, Daniel Beck <[email protected]> wrote: > >> >> On 11.09.2014, at 09:00, Wannes Sels <[email protected]> wrote: >> >> > Can you elaborate on "evil job type"? Is there a specific reason why we >> should avoid maven jobs and go with freestyle? >> >> Stephen's blog: >> >> http://javaadventure.blogspot.de/2013/11/jenkins-maven-job-type-considered-evil.html >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
