You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@taverna.apache.org by Gale Naylor <Ga...@noventussolutions.com> on 2016/09/06 17:22:10 UTC
Question Jenkins build failures
When I look at the Jenkins builds in this link (
https://builds.apache.org/user/stain/my-views/view/taverna/) most of the
builds are failing. There was some discussion recently about the
commandline build failing and needing to upgrade Java and Maven -- or
possibly using different servers? I've read the Jenkins wiki and a few of
the introductory articles, but don't yet understand enough of the process
to know the consequences of failed builds.
Is this a concern, or is it something that typically happens and will
eventually be cleared up? It's just that, since we're referencing the
Jenkins builds in our Graduation Maturity Document, it seems odd that most
of the recent ones are failing.
Thanks,
Gale
Re: Question Jenkins build failures
Posted by Stian Soiland-Reyes <st...@apache.org>.
Thanks, Andy.
I checked on https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
as mentioned on
https://lists.apache.org/thread.html/f6476b1e154c2c9cd8a818aeed8c11e3f77497ac8ed466d7c6b94518@%3Cbuilds.apache.org%3E
We probably now we can use
JDK: JDK 1.8 (latest)
Restrict where this is run: Hadoop||Ubuntu
(It used to be that JDK 8 was not available on all the Ubuntu slaves)
Here's how I do it..
Select a job, e.g.
https://builds.apache.org/user/stain/my-views/view/taverna/job/incubator-taverna-engine/
Configure
Change "JDK" and check Restrct "label" below.
Save
Build Now
wait a bit
check in Build History and find Console to see how it goes.
Repeat for each job :( (No shared configs in Jenkins!)
On 7 September 2016 at 09:02, Andy Seaborne <an...@apache.org> wrote:
>
>
> On 07/09/16 03:44, Stian Soiland-Reyes wrote:
>
>> If you would like to also get Jenkins access (which coul dthen edit
>> any of the jobs), I think any of our mentors could push the button as
>> Andy did for me.
>> http://wiki.apache.org/general/Jenkins
>
>
> Done.
>
--
Stian Soiland-Reyes
http://orcid.org/0000-0001-9842-9718
Re: Question Jenkins build failures
Posted by Andy Seaborne <an...@apache.org>.
On 07/09/16 03:44, Stian Soiland-Reyes wrote:
> If you would like to also get Jenkins access (which coul dthen edit
> any of the jobs), I think any of our mentors could push the button as
> Andy did for me.
> http://wiki.apache.org/general/Jenkins
Done.
Re: Question Jenkins build failures
Posted by Stian Soiland-Reyes <st...@apache.org>.
No, I think we need to go through each of them and edit their config
to use a different jdk-1.8 runtime (I think it's just called "openjdk
1.8 (latest)" .
It's just a bit slow and boring as we have to do it through the web
UI, for each of the builds.. :)
I tried doing it but I'm afraid the server went a bit slow tonight..
If you would like to also get Jenkins access (which coul dthen edit
any of the jobs), I think any of our mentors could push the button as
Andy did for me.
http://wiki.apache.org/general/Jenkins
On 6 September 2016 at 18:22, Gale Naylor <Ga...@noventussolutions.com> wrote:
> When I look at the Jenkins builds in this link (
> https://builds.apache.org/user/stain/my-views/view/taverna/) most of the
> builds are failing. There was some discussion recently about the
> commandline build failing and needing to upgrade Java and Maven -- or
> possibly using different servers? I've read the Jenkins wiki and a few of
> the introductory articles, but don't yet understand enough of the process
> to know the consequences of failed builds.
>
> Is this a concern, or is it something that typically happens and will
> eventually be cleared up? It's just that, since we're referencing the
> Jenkins builds in our Graduation Maturity Document, it seems odd that most
> of the recent ones are failing.
>
> Thanks,
>
> Gale
--
Stian Soiland-Reyes
http://orcid.org/0000-0001-9842-9718