Just want to add to this- freestyle does not have "deploy artifacts" post build step
- freestyle does not have way to use a local maven repository per executor
- freestyle does not have an easy way to use the maven release plugin
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a8424bc3-ccd6-48b1-b5f5-48849bd6848b%40googlegroups.com.
We have 90% of Maven builds. And we switched from maven to freestyle years ago.The things you list are not among the thing I miss, the only one I admit was great was being able to do incremental builds easily.See inline below.2016-06-09 9:39 GMT+02:00 Jorg Heymans <jorg.h...@gmail.com>:Just want to add to this- freestyle does not have "deploy artifacts" post build stepIs `mvn clean deploy -DdeployAtEnd=true` somewhat what you want?What are you trying to achieve with that feature? I never used it, so I'm curious about the use case.
- freestyle does not have way to use a local maven repository per executormaven step, advanced, use private repository. That's in the UI.
- freestyle does not have an easy way to use the maven release pluginThat somewhat seems a definitive statement. As we do hundreds of maven releases using freestyle jobs. Could you give details?You can easily set up either the M2 Release plugin or the more generic Release plugin to achieve that (we used the first, and nowadays have settled on the latter).So yeah maybe it's evil and has issues, but the maven job type is really the only viable option for projects that heavily depend on maven mechanics.Jorg
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS51ihbL3UEcxE1XUN6ZrEq0EbB-0XtQf%2B2TzF1CJ3Xfug%40mail.gmail.com.