> On Wednesday 21 September 2016 13:09:39 Konrad Windszus wrote:
>> Is this a known issue in Pax Exam or in Maven Failsafe? I had a quick look
>> through the open issues in the latter and couldn’t find a report related to
>> our issues. Do you have any references or enough information to report the
On Wednesday 21 September 2016 13:09:39 Konrad Windszus wrote:
> Is this a known issue in Pax Exam or in Maven Failsafe? I had a quick look
> through the open issues in the latter and couldn’t find a report related to
> our issues. Do you have any references or enough information to report the
> is
Is this a known issue in Pax Exam or in Maven Failsafe? I had a quick look
through the open issues in the latter and couldn’t find a report related to our
issues.
Do you have any references or enough information to report the issue upstream?
Thanks,
Konrad
> Am 21.09.2016 um 12:59 schrieb Oliver
On Wednesday 21 September 2016 08:15:12 Carsten Ziegeler wrote:
> It seems the problem on Jenkins was related to the latest failsafe
> plugin, 2.19.1 - I ran into the exact same problem yesterday while
> updating the event IT tests to Oak. Downgrading to 2.18.1 solved the
> problem. So I downgraded
It seems the problem on Jenkins was related to the latest failsafe
plugin, 2.19.1 - I ran into the exact same problem yesterday while
updating the event IT tests to Oak. Downgrading to 2.18.1 solved the
problem. So I downgraded i18n to use that version as well and now it
seems that the project is b
Hi Andrei,
(Kind request - please don't top post, at least not in a long
conversation thread which uses bottom-posting, it's quite hard to
understand what you're replying to :-) )
On Tue, 2016-09-20 at 09:45 +, Andrei Dulvac wrote:
> Hi Robert,
>
> Have a quick look at https://jenkins.io/doc
Hi Robert,
Have a quick look at https://jenkins.io/doc/pipeline/jenkinsfile/
It is a jenkins 1.X plugin, formerly known as "Workflow plugin":
https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin
It is part of jenkins 2.0 now (https://jenkins.io/2.0/) and it will
definitely surpass usage of
On Tue, 2016-09-20 at 09:36 +0200, Bertrand Delacretaz wrote:
> Hi,
>
> On Mon, Sep 19, 2016 at 10:26 PM, Robert Munteanu > wrote:
> >
> > ...Another benefit is that if a contributor wants to reproduce a
> > problem
> > on Jenkins, all the effort that is required is to run Jenkins via
> > docker
Hi,
On Mon, Sep 19, 2016 at 10:26 PM, Robert Munteanu wrote:
> ...Another benefit is that if a contributor wants to reproduce a problem
> on Jenkins, all the effort that is required is to run Jenkins via
> docker, install a couple of plugins, create the seed job and all the
> Jenkins configuratio
On Mon, 2016-09-19 at 23:26 +0300, Robert Munteanu wrote:
> On Mon, 2016-09-19 at 22:50 +0300, Robert Munteanu wrote:
> >
> > I want to use the Job DSL plugin to define a large number of jobs
> > programatically, rather than maintain them by hand.
Here's a more in-depth look at the issue
http:
On Mon, 2016-09-19 at 22:50 +0300, Robert Munteanu wrote:
> I want to use the Job DSL plugin to define a large number of jobs
> programatically, rather than maintain them by hand.
Here's a quick sample of how I intend to use the DSL plugin.
First, I create a 'seed' job, in charge of generating
On Mon, 2016-09-19 at 18:02 +0200, Konrad Windszus wrote:
> Wouldn’t it make more sense to rely on the pipeline plugin instead of
> the Job DSL Plugin? This is by default shipped in Jenkins since 2.0.0
> so probably there is not even the necessity to install an additional
> plugin.
> For a comparis
+1 to the pipeline plugin.
Info on the other CI builds.
There is a build that builds pull requests from GitHub in Jenkins, IIRC its
only JDK8 and doesn't have tests enabled as there were too many false
negatives, but I would need to check that.
Also there are Travis CI builds for JDK8 and JDK7, th
Was going to write the exact same thing. The pipeline plugin, now just
"pipeline" into jenkins 2, is the future and I would recommend using it.
Except if there are plugins you want to use that are not supported yet.
-Andrei
On Mon, Sep 19, 2016 at 6:02 PM Konrad Windszus wrote:
> Wouldn’t it ma
> Hi Carsten,
>
> It looks like we have a different classpath when it fails and when it
> doesn't
> Maybe you can put a mvn dependency:tree in the job and check how it looks
> in the two cases.
>
> Also, AFAIK the fact that the maven dependency resolution mechanism puts
> the ones defined in the
Wouldn’t it make more sense to rely on the pipeline plugin instead of the Job
DSL Plugin? This is by default shipped in Jenkins since 2.0.0 so probably there
is not even the necessity to install an additional plugin.
For a comparison between those two approaches look at
http://stackoverflow.com/
Hi Carsten,
It looks like we have a different classpath when it fails and when it
doesn't
Maybe you can put a mvn dependency:tree in the job and check how it looks
in the two cases.
Also, AFAIK the fact that the maven dependency resolution mechanism puts
the ones defined in the project pom and re
On Mon, 2016-09-19 at 16:39 +0200, Carsten Ziegeler wrote:
> >
> > On Mon, 2016-09-19 at 15:53 +0200, Carsten Ziegeler wrote:
> > >
> > > The benefit of the current solution is clear: below or equal to
> > > zero.
> > > Afaik, Robert look already into having per module jobs in
> > > jenkins.
> >
> On Mon, 2016-09-19 at 15:53 +0200, Carsten Ziegeler wrote:
>> The benefit of the current solution is clear: below or equal to zero.
>> Afaik, Robert look already into having per module jobs in jenkins.
>> Not
>> sure how far this is.
>
> I pinged infra about this and noone opposed :-)
>
> htt
On Mon, 2016-09-19 at 15:53 +0200, Carsten Ziegeler wrote:
> The benefit of the current solution is clear: below or equal to zero.
> Afaik, Robert look already into having per module jobs in jenkins.
> Not
> sure how far this is.
I pinged infra about this and noone opposed :-)
http://mail-archi
The benefit of the current solution is clear: below or equal to zero.
Afaik, Robert look already into having per module jobs in jenkins. Not
sure how far this is.
Carsten
> +1 for openly talking about this. I think the most important thing is
> clearly understanding the benefits and drawbacks for
+1 for openly talking about this. I think the most important thing is
clearly understanding the benefits and drawbacks for the different ways of
building continuously.
On Mon, Sep 19, 2016 at 3:43 PM Stefan Seifert
wrote:
> > for quiet some time now, it seems that the IT tests of the i18n module
> for quiet some time now, it seems that the IT tests of the i18n module fail
> in reactor build
i also had a brief look at the tests of the i18n project and was not able to
spot the problem easily.
>I suggest we turn off Jenkins completely
do we have an alternative?
ian invested a good amoun
>> Hi,
>>
>> for quiet some time now, it seems that the IT tests of the i18n module
>> fail in reactor build (at least, Jenkins seems to fail all the time).
>> Interestingly, I can only reproduce this from time to time. However when
>> it fails, it fails with:
>>
>> Tests run: 3, Failures: 0, Error
> Hi,
>
> for quiet some time now, it seems that the IT tests of the i18n module
> fail in reactor build (at least, Jenkins seems to fail all the time).
> Interestingly, I can only reproduce this from time to time. However when
> it fails, it fails with:
>
> Tests run: 3, Failures: 0, Errors: 2,
Hi,
for quiet some time now, it seems that the IT tests of the i18n module
fail in reactor build (at least, Jenkins seems to fail all the time).
Interestingly, I can only reproduce this from time to time. However when
it fails, it fails with:
Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time
26 matches
Mail list logo
