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 <[email protected]> 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
