You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Ralph Goers <ra...@dslextreme.com> on 2021/04/05 02:09:22 UTC
Jenkins build
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
Re: Jenkins build
Posted by Matt Sicker <bo...@gmail.com>.
The Windows build doesn't seem to be the issue. It seems to be related
to running mvn deploy for the snapshot. See logs:
https://ci-builds.apache.org/job/Logging/job/log4j/job/master/256/console
On Mon, 5 Apr 2021 at 16:34, Matt Sicker <bo...@gmail.com> wrote:
>
> Alright, the Linux side passed, but the Windows side had a
> module-related import error with OSGi.
>
> On Mon, 5 Apr 2021 at 16:21, Matt Sicker <bo...@gmail.com> wrote:
> >
> > I've updated the mvn step to use Java 11 on the master branch. That
> > will apply to any other pipelines using this at the moment, but that
> > shouldn't be a problem for now.
> >
> > On Mon, 5 Apr 2021 at 09:30, Matt Sicker <bo...@gmail.com> wrote:
> > >
> > > Also, Jenkins docs are usually in Jenkins itself like these useful
> > > pages (I reference them every time I need to make non-trivial
> > > changes):
> > >
> > > https://ci-builds.apache.org/job/Logging/job/log4j/pipeline-syntax/
> > > https://ci-builds.apache.org/job/Logging/job/log4j/pipeline-syntax/html
> > > (warning: loooooong page)
> > > https://ci-builds.apache.org/job/Logging/job/log4j/pipeline-syntax/globals
> > >
> > > On Mon, 5 Apr 2021 at 09:27, Matt Sicker <bo...@gmail.com> wrote:
> > > >
> > > > 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 <ra...@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 <bo...@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 <ra...@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
> > > > > >>
> > > > >
> > > > >
Re: Jenkins build
Posted by Matt Sicker <bo...@gmail.com>.
Alright, the Linux side passed, but the Windows side had a
module-related import error with OSGi.
On Mon, 5 Apr 2021 at 16:21, Matt Sicker <bo...@gmail.com> wrote:
>
> I've updated the mvn step to use Java 11 on the master branch. That
> will apply to any other pipelines using this at the moment, but that
> shouldn't be a problem for now.
>
> On Mon, 5 Apr 2021 at 09:30, Matt Sicker <bo...@gmail.com> wrote:
> >
> > Also, Jenkins docs are usually in Jenkins itself like these useful
> > pages (I reference them every time I need to make non-trivial
> > changes):
> >
> > https://ci-builds.apache.org/job/Logging/job/log4j/pipeline-syntax/
> > https://ci-builds.apache.org/job/Logging/job/log4j/pipeline-syntax/html
> > (warning: loooooong page)
> > https://ci-builds.apache.org/job/Logging/job/log4j/pipeline-syntax/globals
> >
> > On Mon, 5 Apr 2021 at 09:27, Matt Sicker <bo...@gmail.com> wrote:
> > >
> > > 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 <ra...@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 <bo...@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 <ra...@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
> > > > >>
> > > >
> > > >
Re: Jenkins build
Posted by Matt Sicker <bo...@gmail.com>.
I've updated the mvn step to use Java 11 on the master branch. That
will apply to any other pipelines using this at the moment, but that
shouldn't be a problem for now.
On Mon, 5 Apr 2021 at 09:30, Matt Sicker <bo...@gmail.com> wrote:
>
> Also, Jenkins docs are usually in Jenkins itself like these useful
> pages (I reference them every time I need to make non-trivial
> changes):
>
> https://ci-builds.apache.org/job/Logging/job/log4j/pipeline-syntax/
> https://ci-builds.apache.org/job/Logging/job/log4j/pipeline-syntax/html
> (warning: loooooong page)
> https://ci-builds.apache.org/job/Logging/job/log4j/pipeline-syntax/globals
>
> On Mon, 5 Apr 2021 at 09:27, Matt Sicker <bo...@gmail.com> wrote:
> >
> > 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 <ra...@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 <bo...@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 <ra...@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
> > > >>
> > >
> > >
Re: Jenkins build
Posted by Matt Sicker <bo...@gmail.com>.
Also, Jenkins docs are usually in Jenkins itself like these useful
pages (I reference them every time I need to make non-trivial
changes):
https://ci-builds.apache.org/job/Logging/job/log4j/pipeline-syntax/
https://ci-builds.apache.org/job/Logging/job/log4j/pipeline-syntax/html
(warning: loooooong page)
https://ci-builds.apache.org/job/Logging/job/log4j/pipeline-syntax/globals
On Mon, 5 Apr 2021 at 09:27, Matt Sicker <bo...@gmail.com> wrote:
>
> 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 <ra...@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 <bo...@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 <ra...@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
> > >>
> >
> >
Re: Jenkins build
Posted by Matt Sicker <bo...@gmail.com>.
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 <ra...@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 <bo...@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 <ra...@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
> >>
>
>
Re: Jenkins build
Posted by Ralph Goers <ra...@dslextreme.com>.
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 <bo...@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 <ra...@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
>>
Re: Jenkins build
Posted by Matt Sicker <bo...@gmail.com>.
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 <ra...@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
>