You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Matt Sicker <bo...@gmail.com> on 2018/04/10 16:57:04 UTC
[Log4j] Jenkins pipeline mostly set up
I've added a new pipeline for Log4j <
https://builds.apache.org/job/Log4jCore/> using a Jenkinsfile as we are
doing in log4net, chainsaw, log4j scala api, log4j kotlin api, and logging
parent. Thanks to Dominik for demonstrating that this was possible and also
how to run things on Windows.
This pipeline is configured to run the build in parallel on three platforms:
* Ubuntu with Oracle JDK 8 and 9
* Ubuntu with IBM JDK 8 and Oracle JDK 9 (waiting to see if infra adds
OpenJ9 or at least a JDK9 version of the IBM JDK as an option to make this
pipeline fully IBM)
* Windows with Oracle JDK 8 and 9
This is configured to fail fast if any one of those three builds fail.
Afterwards, it archives test results and uploads snapshots to
repository.a.o. Now I haven't seen all three builds pass together yet
(there appears to be an issue with the embedded mongo tests that I don't
know how to reproduce locally), but it's almost there! I'm considering
ignoring those tests on jenkins for now to make sure everything else builds
fine.
Once this pipeline is stabilized, we can remove the old windows jenkins
project as well as the old log4j 2 3.x project. We can leave the
release-2.x branch project available, or I can backport the jenkins
pipeline to that branch as well to get rid of unnecessary jenkins projects.
--
Matt Sicker <bo...@gmail.com>
Re: [Log4j] Jenkins pipeline mostly set up
Posted by Ralph Goers <ra...@dslextreme.com>.
If you are using mvn deploy then it should upload correctly as the various modules have the deploy plugin disabled.
Ralph
> On Apr 11, 2018, at 7:44 AM, Matt Sicker <bo...@gmail.com> wrote:
>
> I’ve set it up to use the “mvn deploy” task to upload. Only automatic thing
> about Jenkins here is that the m2 settings.xml is provided or something so
> that you don’t need to configure a user to upload with (like I had to do
> for the sbt build).
>
> Anyways, if I see how to customize that in maven, I’ll update log4j as well.
>
> On Wed, Apr 11, 2018 at 00:16, Ralph Goers <ra...@dslextreme.com>
> wrote:
>
>> I don’t know. I have never really looked at how Jenkins does the deploy.
>>
>> Ralph
>>
>>> On Apr 10, 2018, at 7:16 PM, Matt Sicker <bo...@gmail.com> wrote:
>>>
>>> Is it possible to exclude that from the deploy task? The scala api build
>>> only publishes the api jars, not the samples, for example.
>>>
>>> On 10 April 2018 at 17:12, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>>
>>>> Note that the Jenkins deployment uploads stuff that we don’t release.
>>>>
>>>> Ralph
>>>>
>>>>> On Apr 10, 2018, at 9:57 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>>>
>>>>> I've added a new pipeline for Log4j <
>>>>> https://builds.apache.org/job/Log4jCore/> using a Jenkinsfile as we
>> are
>>>>> doing in log4net, chainsaw, log4j scala api, log4j kotlin api, and
>>>> logging
>>>>> parent. Thanks to Dominik for demonstrating that this was possible and
>>>> also
>>>>> how to run things on Windows.
>>>>>
>>>>> This pipeline is configured to run the build in parallel on three
>>>> platforms:
>>>>> * Ubuntu with Oracle JDK 8 and 9
>>>>> * Ubuntu with IBM JDK 8 and Oracle JDK 9 (waiting to see if infra adds
>>>>> OpenJ9 or at least a JDK9 version of the IBM JDK as an option to make
>>>> this
>>>>> pipeline fully IBM)
>>>>> * Windows with Oracle JDK 8 and 9
>>>>>
>>>>> This is configured to fail fast if any one of those three builds fail.
>>>>> Afterwards, it archives test results and uploads snapshots to
>>>>> repository.a.o. Now I haven't seen all three builds pass together yet
>>>>> (there appears to be an issue with the embedded mongo tests that I
>> don't
>>>>> know how to reproduce locally), but it's almost there! I'm considering
>>>>> ignoring those tests on jenkins for now to make sure everything else
>>>> builds
>>>>> fine.
>>>>>
>>>>> Once this pipeline is stabilized, we can remove the old windows jenkins
>>>>> project as well as the old log4j 2 3.x project. We can leave the
>>>>> release-2.x branch project available, or I can backport the jenkins
>>>>> pipeline to that branch as well to get rid of unnecessary jenkins
>>>> projects.
>>>>>
>>>>> --
>>>>> Matt Sicker <bo...@gmail.com>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>
>>
>> --
> Matt Sicker <bo...@gmail.com>
Re: [Log4j] Jenkins pipeline mostly set up
Posted by Matt Sicker <bo...@gmail.com>.
I’ve set it up to use the “mvn deploy” task to upload. Only automatic thing
about Jenkins here is that the m2 settings.xml is provided or something so
that you don’t need to configure a user to upload with (like I had to do
for the sbt build).
Anyways, if I see how to customize that in maven, I’ll update log4j as well.
On Wed, Apr 11, 2018 at 00:16, Ralph Goers <ra...@dslextreme.com>
wrote:
> I don’t know. I have never really looked at how Jenkins does the deploy.
>
> Ralph
>
> > On Apr 10, 2018, at 7:16 PM, Matt Sicker <bo...@gmail.com> wrote:
> >
> > Is it possible to exclude that from the deploy task? The scala api build
> > only publishes the api jars, not the samples, for example.
> >
> > On 10 April 2018 at 17:12, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >
> >> Note that the Jenkins deployment uploads stuff that we don’t release.
> >>
> >> Ralph
> >>
> >>> On Apr 10, 2018, at 9:57 AM, Matt Sicker <bo...@gmail.com> wrote:
> >>>
> >>> I've added a new pipeline for Log4j <
> >>> https://builds.apache.org/job/Log4jCore/> using a Jenkinsfile as we
> are
> >>> doing in log4net, chainsaw, log4j scala api, log4j kotlin api, and
> >> logging
> >>> parent. Thanks to Dominik for demonstrating that this was possible and
> >> also
> >>> how to run things on Windows.
> >>>
> >>> This pipeline is configured to run the build in parallel on three
> >> platforms:
> >>> * Ubuntu with Oracle JDK 8 and 9
> >>> * Ubuntu with IBM JDK 8 and Oracle JDK 9 (waiting to see if infra adds
> >>> OpenJ9 or at least a JDK9 version of the IBM JDK as an option to make
> >> this
> >>> pipeline fully IBM)
> >>> * Windows with Oracle JDK 8 and 9
> >>>
> >>> This is configured to fail fast if any one of those three builds fail.
> >>> Afterwards, it archives test results and uploads snapshots to
> >>> repository.a.o. Now I haven't seen all three builds pass together yet
> >>> (there appears to be an issue with the embedded mongo tests that I
> don't
> >>> know how to reproduce locally), but it's almost there! I'm considering
> >>> ignoring those tests on jenkins for now to make sure everything else
> >> builds
> >>> fine.
> >>>
> >>> Once this pipeline is stabilized, we can remove the old windows jenkins
> >>> project as well as the old log4j 2 3.x project. We can leave the
> >>> release-2.x branch project available, or I can backport the jenkins
> >>> pipeline to that branch as well to get rid of unnecessary jenkins
> >> projects.
> >>>
> >>> --
> >>> Matt Sicker <bo...@gmail.com>
> >>
> >>
> >>
> >
> >
> > --
> > Matt Sicker <bo...@gmail.com>
>
>
> --
Matt Sicker <bo...@gmail.com>
Re: [Log4j] Jenkins pipeline mostly set up
Posted by Ralph Goers <ra...@dslextreme.com>.
I don’t know. I have never really looked at how Jenkins does the deploy.
Ralph
> On Apr 10, 2018, at 7:16 PM, Matt Sicker <bo...@gmail.com> wrote:
>
> Is it possible to exclude that from the deploy task? The scala api build
> only publishes the api jars, not the samples, for example.
>
> On 10 April 2018 at 17:12, Ralph Goers <ra...@dslextreme.com> wrote:
>
>> Note that the Jenkins deployment uploads stuff that we don’t release.
>>
>> Ralph
>>
>>> On Apr 10, 2018, at 9:57 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>
>>> I've added a new pipeline for Log4j <
>>> https://builds.apache.org/job/Log4jCore/> using a Jenkinsfile as we are
>>> doing in log4net, chainsaw, log4j scala api, log4j kotlin api, and
>> logging
>>> parent. Thanks to Dominik for demonstrating that this was possible and
>> also
>>> how to run things on Windows.
>>>
>>> This pipeline is configured to run the build in parallel on three
>> platforms:
>>> * Ubuntu with Oracle JDK 8 and 9
>>> * Ubuntu with IBM JDK 8 and Oracle JDK 9 (waiting to see if infra adds
>>> OpenJ9 or at least a JDK9 version of the IBM JDK as an option to make
>> this
>>> pipeline fully IBM)
>>> * Windows with Oracle JDK 8 and 9
>>>
>>> This is configured to fail fast if any one of those three builds fail.
>>> Afterwards, it archives test results and uploads snapshots to
>>> repository.a.o. Now I haven't seen all three builds pass together yet
>>> (there appears to be an issue with the embedded mongo tests that I don't
>>> know how to reproduce locally), but it's almost there! I'm considering
>>> ignoring those tests on jenkins for now to make sure everything else
>> builds
>>> fine.
>>>
>>> Once this pipeline is stabilized, we can remove the old windows jenkins
>>> project as well as the old log4j 2 3.x project. We can leave the
>>> release-2.x branch project available, or I can backport the jenkins
>>> pipeline to that branch as well to get rid of unnecessary jenkins
>> projects.
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>
>>
>>
>
>
> --
> Matt Sicker <bo...@gmail.com>
Re: [Log4j] Jenkins pipeline mostly set up
Posted by Matt Sicker <bo...@gmail.com>.
Is it possible to exclude that from the deploy task? The scala api build
only publishes the api jars, not the samples, for example.
On 10 April 2018 at 17:12, Ralph Goers <ra...@dslextreme.com> wrote:
> Note that the Jenkins deployment uploads stuff that we don’t release.
>
> Ralph
>
> > On Apr 10, 2018, at 9:57 AM, Matt Sicker <bo...@gmail.com> wrote:
> >
> > I've added a new pipeline for Log4j <
> > https://builds.apache.org/job/Log4jCore/> using a Jenkinsfile as we are
> > doing in log4net, chainsaw, log4j scala api, log4j kotlin api, and
> logging
> > parent. Thanks to Dominik for demonstrating that this was possible and
> also
> > how to run things on Windows.
> >
> > This pipeline is configured to run the build in parallel on three
> platforms:
> > * Ubuntu with Oracle JDK 8 and 9
> > * Ubuntu with IBM JDK 8 and Oracle JDK 9 (waiting to see if infra adds
> > OpenJ9 or at least a JDK9 version of the IBM JDK as an option to make
> this
> > pipeline fully IBM)
> > * Windows with Oracle JDK 8 and 9
> >
> > This is configured to fail fast if any one of those three builds fail.
> > Afterwards, it archives test results and uploads snapshots to
> > repository.a.o. Now I haven't seen all three builds pass together yet
> > (there appears to be an issue with the embedded mongo tests that I don't
> > know how to reproduce locally), but it's almost there! I'm considering
> > ignoring those tests on jenkins for now to make sure everything else
> builds
> > fine.
> >
> > Once this pipeline is stabilized, we can remove the old windows jenkins
> > project as well as the old log4j 2 3.x project. We can leave the
> > release-2.x branch project available, or I can backport the jenkins
> > pipeline to that branch as well to get rid of unnecessary jenkins
> projects.
> >
> > --
> > Matt Sicker <bo...@gmail.com>
>
>
>
--
Matt Sicker <bo...@gmail.com>
Re: [Log4j] Jenkins pipeline mostly set up
Posted by Ralph Goers <ra...@dslextreme.com>.
Note that the Jenkins deployment uploads stuff that we don’t release.
Ralph
> On Apr 10, 2018, at 9:57 AM, Matt Sicker <bo...@gmail.com> wrote:
>
> I've added a new pipeline for Log4j <
> https://builds.apache.org/job/Log4jCore/> using a Jenkinsfile as we are
> doing in log4net, chainsaw, log4j scala api, log4j kotlin api, and logging
> parent. Thanks to Dominik for demonstrating that this was possible and also
> how to run things on Windows.
>
> This pipeline is configured to run the build in parallel on three platforms:
> * Ubuntu with Oracle JDK 8 and 9
> * Ubuntu with IBM JDK 8 and Oracle JDK 9 (waiting to see if infra adds
> OpenJ9 or at least a JDK9 version of the IBM JDK as an option to make this
> pipeline fully IBM)
> * Windows with Oracle JDK 8 and 9
>
> This is configured to fail fast if any one of those three builds fail.
> Afterwards, it archives test results and uploads snapshots to
> repository.a.o. Now I haven't seen all three builds pass together yet
> (there appears to be an issue with the embedded mongo tests that I don't
> know how to reproduce locally), but it's almost there! I'm considering
> ignoring those tests on jenkins for now to make sure everything else builds
> fine.
>
> Once this pipeline is stabilized, we can remove the old windows jenkins
> project as well as the old log4j 2 3.x project. We can leave the
> release-2.x branch project available, or I can backport the jenkins
> pipeline to that branch as well to get rid of unnecessary jenkins projects.
>
> --
> Matt Sicker <bo...@gmail.com>