On Sun, Jun 12, 2016 at 2:48 PM, Baptiste Mathus wrote:
> 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.
>
>
So Baptiste, how did you handle the matter of triggering build of dependent
modules?
Do you have one job per module or is it more one job for a multimodule
project without dependencies to other jobs's modules?
Here we have something like 200 jobs for 200 maven modules and we rely
extensively
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 :
>
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
So yeah maybe it's evil and has issues, but the maven job type is
Anybody? It seems an important issue to me…
Thanks,
Victor
Le lundi 8 juin 2015 10:21:46 UTC+2, Victor Noël a écrit :
Hi,
Following the switch to Java 7+, many users have problem with the
Maven-style jobs: they are forbidden to execute them with a version of Java
inferior to 7.
See for
There is no automated mechanism.
On Mon, Jun 15, 2015 at 5:50 AM, Victor Noël victor.n...@gmail.com wrote:
Anybody? It seems an important issue to me…
Thanks,
Victor
Le lundi 8 juin 2015 10:21:46 UTC+2, Victor Noël a écrit :
Hi,
Following the switch to Java 7+, many users have problem
Hi,
Following the switch to Java 7+, many users have problem with the
Maven-style jobs: they are forbidden to execute them with a version of Java
inferior to 7.
See for example https://issues.jenkins-ci.org/browse/JENKINS-28294.
The common solution proposed by people is to switch to Freestyle