Oh, well, since the tool locations still seem to be the same (they're
the same nodes after all), hard-coding the JAVA_HOME and PATH+MAVEN
environment variables worked fine. I had initially tried using a
toolchains.xml pointing to all the JDKs installed (well, from 8 to 14
at least) along with using maven-wrapper, but the build in question
wasn't properly configured to build without JAVA_HOME set as well, so
I had to devise this workaround. Otherwise, you can just use the tool
DSL to automatically configure the JDK and Maven setup as usual (which
also means you'd be able to use JAVA_HOME=${lib 'JDK 1.8 (latest)'} in
the withEnv step rather than hardcoding the path as the tool step
returns the path to the tool home (after installing said tool if
needed).For the toolchains.xml, I stored those as config files on Jenkins, though it'd be nice to either have a global toolchains.xml configured on each node, or to have global config files in Jenkins that any job can use (I stored mine in the Logging folder). On Mon, 27 Jul 2020 at 09:52, Gavin McDonald <gmcdon...@apache.org> wrote: > > Hi All, > > > On Mon, Jul 27, 2020 at 4:48 PM Matt Sicker <boa...@gmail.com> wrote: > > > FYI, the toolchains configFileProvider thing is only needed for > > multi-JDK builds (like in Log4j). The withEnv is the important part > > here. > > > > Yes. we have our tool locations in Puppet to popuate the mappings of the > JDKs, Maven > and Ant to the proper windows locations. The modules erb template needs a > tweak as > the shared windows agent config.xml is drastically different from the > standard. There are > now also uids and plugin versions mentioned now in these config files, so > might end up > having to do some groovy init script or something like that, to populate > the tool > locations on the win nodes. > > Gav > > > > On Mon, 27 Jul 2020 at 09:47, Matt Sicker <boa...@gmail.com> wrote: > > > > > > I was unable to get Maven to work using the tool DSL initially, but I > > > did manage to get it working with manual PATH setup: > > > > > > https://github.com/apache/logging-pipelines/blob/master/vars/mvn.groovy > > > > > > On Mon, 27 Jul 2020 at 05:54, sebb <seb...@gmail.com> wrote: > > > > > > > > What software is installed on the Windows nodes? > > > > > > > > I was able to find a version of Maven -- 'latest' does not work -- > > > > however could not work out how to specify Java for Windows. > > > > This is for > > https://ci-builds.apache.org/job/Commons/job/commons-net-windows/ > > > > > > > > On Sat, 25 Jul 2020 at 14:39, Chris Thistlethwaite <chr...@apache.org> > > wrote: > > > > > > > > > > Greetings! > > > > > > > > > > If you've been looking on builds.a.o recently you've likely noticed > > that > > > > > we're down to 2 Windows nodes. Fear not! They have been moved to > > > > > jenkins-ccos.a.o as shared agents for all to use! I know, super > > exciting > > > > > news on a Saturday, I'm sure you've likely spit out your Wheaties in > > > > > excitement. > > > > > > > > > > The 'Windows' label will continue to work on both old and new build > > > > > servers. That is until we turn off builds.a.o on August 15th, so > > > > > remember to migrate your jobs. > > > > > > > > > > Have a great weekend! > > > > > > > > > > -Chris T. > > > > > #asfinfra > > > > > > > > > > > > -- > > > Matt Sicker <boa...@gmail.com> > > > > > > > > -- > > Matt Sicker <boa...@gmail.com> > > > > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team -- Matt Sicker <boa...@gmail.com>
