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.
