You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jclouds.apache.org by BuildHive <bu...@cloudbees.com> on 2013/07/01 22:00:50 UTC

Jenkins build became unstable: jclouds » jclouds-labs-aws #121

See <https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-aws/121/>

Re: Jenkins build became unstable: jclouds » jclouds-labs-aws #121

Posted by Andrew Bayer <an...@gmail.com>.

And yup, that was it. Next build will be good.

A.

On Mon, Jul 1, 2013 at 1:38 PM, Andrew Bayer <an...@gmail.com> wrote:

> Pretty sure this was just a bad luck race condition, with the build
> getting the new build of ec2 but not the new build of aws-ec2. Verifying
> locally.
>
> A.
>
> On Mon, Jul 1, 2013 at 1:00 PM, BuildHive <bu...@cloudbees.com>wrote:
>
>> See <
>> https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-aws/121/>
>>
>>
>

Re: Jenkins build became unstable: jclouds » jclouds-labs-aws #121

Posted by Andrew Bayer <an...@gmail.com>.

Pretty sure this was just a bad luck race condition, with the build getting
the new build of ec2 but not the new build of aws-ec2. Verifying locally.

A.

On Mon, Jul 1, 2013 at 1:00 PM, BuildHive <bu...@cloudbees.com>wrote:

> See <https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-aws/121/
> >
>
>

Jenkins build is back to stable : jclouds » jclouds-labs-aws #122

Posted by BuildHive <bu...@cloudbees.com>.

See <https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-aws/122/>