Hi,
On Sun, Jul 31, 2016 at 3:09 AM, khmarbaise wrote:
>
>> enforcement, other stuff). So for example, running a clean install and
>> skipping all tests on a typical project versus clean install yields
>> about 10-20% reduction in wall clock execution time.
>
> Skipping Test will of course reduce
On Sunday, July 31, 2016 at 1:26:58 AM UTC+2, Jesse Farinacci wrote:
>
> Hi,
>
> On Sat, Jul 30, 2016 at 2:39 PM, khmarbaise > wrote:
> > so have you really measured the time you are "wasting" ? Furthermore
> which
> > Maven version and plugin versions do you use? Are you using freestyle or
Hi,
On Sat, Jul 30, 2016 at 2:39 PM, khmarbaise wrote:
> so have you really measured the time you are "wasting" ? Furthermore which
> Maven version and plugin versions do you use? Are you using freestyle or
> Maven job type...
Yes, we have measured. Both with the Tesla Maven Profiler, but also
Hi,
so have you really measured the time you are "wasting" ? Furthermore which
Maven version and plugin versions do you use? Are you using freestyle or
Maven job type...
On Saturday, July 30, 2016 at 8:13:14 PM UTC+2, Jesse Farinacci wrote:
>
> My team faces similar challenges, and I agree with
My team faces similar challenges, and I agree with almost everything
said so far. I definitely echo the sentiment that it feels like there
is a lot of wasted repetition when invoking discrete phases
separately. We currently do this via separate jobs now, which often
run at different frequencies. Ho
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 c
Thanks for your feedbacks!
So in the end, what is the solution you adopted? more coarse grained stages?
Le dimanche 24 juillet 2016 14:18:18 UTC+2, wo...@anomalizer.net a écrit :
>
> Hello Victor,
>
> I am faced with a similar problem and gave up on the idea rather early on.
> Here are some of t
Hello Victor,
I am faced with a similar problem and gave up on the idea rather early on.
Here are some of the characteristics of multiple stages of a pipeline
- Ability of each stage to be explictly invoked by some command
- Ability of each stage to be re-run in such a way that it can star
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
