maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Connolly <stephen.alan.conno...@gmail.com>
Subject Re: Jenkins job stability: was Re: [MNG-5551] Java 8 + Maven status
Date Sat, 29 Mar 2014 14:12:11 GMT
I don't have the time to explain how I want to add maven support to the
literate job type

On Saturday, 29 March 2014, Hervé BOUTEMY <herve.boutemy@free.fr> wrote:

> I don't understand how pipelines will change anything to the staging issue
>
> Regards,
>
> Hervé
>
> Le vendredi 28 mars 2014 14:53:56 Mirko Friedenhagen a écrit :
> > Hello Stephen,
> >
> > I am a big fan of pipelines here:
> >
> > 1. clean test-compile
> > 2. clean verify of modules with changes or excluding failsafe/invoker
> > 3. clean verify of all modules with inclusion of invoker tests.
> >
> > Regards
> > Mirko
> >
> > > I would rather get some good pipelining going so that we have a better
> > > quality of jobs in the first place, e.g. see the job pipeline I have
> set
> > > up
> > > https://builds.apache.org/job/maven-3.2-release-status/
> > >
> > > I want to add other tests into this pipeline and once we have a strong
> > > template for a good pipeline then we can replicate for other needs
> (note
> > > that the reality is I will transfer the pipeline to the literate job
> type
> > > once I get that out the door as it makes the whole shebang a whole lot
> > > easier to setup and visualize... plus it makes branch development nicer
> > > too)
> > >
> > >
> > > On 28 March 2014 11:32, Mirko Friedenhagen <mfriedenhagen@gmail.com>
> > >
> > > wrote:
> > > > Hello,
> > > >
> > > > as a fresh subscriber to notifications I really wonder how often the
> > > > jobs
> > > > have failed in the last two weeks.
> > > >
> > > > - One reason seems to be, that during staging of plugins and
> especially
> > > > shared components the jobs are failing because of staged dependencies
> > > > are
> > > > not available in central. I proposed to include all of maven-staging
> to
> > >
> > > the
> > >
> > > > settings of Jenkins for IT and shared, but there were some concerns
> by
> > > > Karl-Heinz(?) Same goes for the pom staging.
> > > > - Yesterday maven-dependency-analyzer was not able to compile it's
> > > > tests,
> > > > because the TestCase symbol from junit was missing, my guess would
> be a
> > > > defect local repository because of concurrent downloads.
> > > > - All in all right now the jobs do irritate me more than help me.
> > > > - IMO once a Jenkins job fails oftenly out of the blue it rapidly
> starts
> > >
> > > to
> > >
> > > > become useless :-)
> > > >
> > > > So I have two proposals:
> > > > - Include maven-staging in a special settings file included in
> > >
> > > maven-shared
> > >
> > > > and maven-plugin only to be used in Jenkins.
> > > > - Configure jobs to use a private repository in the Jenkins workspace
> > > > and
> > > > purge it beforehand.
> > > >
> > > > What do you think?
> > > >
> > > > Regards
> > > > Mirko
> > > > --
> > > > Sent from my mobile
> > > > On Mar 28, 2014 8:12 AM, "Hervé BOUTEMY" <herve.boutemy@free.fr>
> wrote:
> > > >
> > > > why didn't we detect the failure when building the plugin and running
> > > > ITs
> > > > with
> > > > JDK 8 = somthing we did a long time ago and that I was conviced would
> > >
> > > give
> > >
> > > > us
> > > > more accurate results than what we finally have?
> > > >
> > > > I had a quick look at ITs, and it seems that the compiler plugin is
> > > > configured
> > > > to generate 1.5 bytecode
> > > > IMHO, we need to add an IT generating 1.8 bytecode to make tests and
> > > > show
> > > > the
> > > > failure before fixing and being sure the fix is complete.
> > > > I didn't have time to really test, but I hope such discussion can
> help
> > > > us
> > > > improve JDK8 support more rapidly
> > > > And find every other place where JDK8 compatibility won't be
> automatic:
> > > > looking
> > > > for asm is one way, but I suppose there may be problems for tools not
> > >
> > > using
> > >
> > > > asm
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > Le vendredi 28 mars 2014 07:40:53 Kristian Rosenvold a écrit :
> > > > > I have updated dependency (maven shade) to use asm 5.0.1, and I
> hope
> > > > > to
> > > >
> > > > get
> > > >
> > > > > version 0.8 of dependency released RealSoon (tm).
> > > > >
> > > > > Kristian
> > > > >
> > > > > 2014-03-27 21:16 GMT+01:00 Mirko Friedenhagen > > > >
> To
> unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
> > > > > > For additional commands, e-mail: dev-help@maven.apache.org<javascript:;>
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org<javascript:;>
> > > > For additional commands, e-mail: dev-help@maven.apache.org<javascript:;>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
> For additional commands, e-mail: dev-help@maven.apache.org <javascript:;>
>
>

-- 
Sent from my phone

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message