https://github.com/apache/struts/blob/777caaade067b755b9aa4638f28ba8579d1c7a1d/Jenkinsfile#L32-L34 is the gist of how it's normally supposed to be configured for the sh/bat steps. I'll figure out a specific fix later today.
On Sun, 4 Apr 2021 at 23:25, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > Yes, I saw the mvn command. But I couldn’t figure out what logic to use to > get it to only use Java 11 for Log4j master since this seems to be used for > multiple builds. I can’t seem to find clear docs on all the variables or > methods that are available to use in a groovy script. I admit to being a > novice when it comes to Jenkins pipelines. We use them at work and almost no > engineers understand them. > > Ralph > > > On Apr 4, 2021, at 9:17 PM, Matt Sicker <boa...@gmail.com> wrote: > > > > Yeah, I can update it. I used a workaround a while ago with hard coded JDKs > > which probably has a simpler approach now. The mvn command is in the vars > > directory. > > > > On Sun, Apr 4, 2021 at 21:09 Ralph Goers <ralph.go...@dslextreme.com> wrote: > > > >> Matt, > >> > >> I just noticed that the build for Log4j 2 Master is failing. I guess you > >> must have modified the configuration a while ago. I had thought each > >> project had their own Jenkins file but it appears they are all now sharing > >> one in the logging-pipelines project. I took a look at that project but I > >> really have no idea how to modify it property. The pipeline seems to > >> implement an “mvn” command as a groovy script that sets up the toolchains > >> and Java 8 as the default. The problem is master no longer uses toolchains > >> and has upgraded to Java 11. I have no idea how to detect that this is the > >> build for the log4j master branch vs some other project. > >> > >> It does seem like having something in the project might have helped this > >> situation. > >> > >> Can you possibly look at this? > >> > >> Ralph > >> > >
