I've copied the Jenkinsfile over to release-2.x. I've disabled the
four existing Maven jobs in Jenkins and added links to the pipeline in
their descriptions. Last thing remaining will be email notifications
again, though I have that set up to ping #logging on the-asf Slack.
Please let me know what your preferences are for notification emails
so I can add it to the Jenkinsfile.

On Fri, 3 Apr 2020 at 21:30, Matt Sicker <boa...@gmail.com> wrote:
>
> Small update: the URL can also be accessed directly through the job
> name rather than via the view:
>
> https://builds.apache.org/job/log4j/
>
> Easy URL to remember, too. ;)
>
> On Fri, 3 Apr 2020 at 20:28, Matt Sicker <boa...@gmail.com> wrote:
> >
> > I've deleted some old pipelines in Jenkins and am updating the one in
> > master to work properly. The job is located here:
> >
> > https://builds.apache.org/view/L/view/Logging/job/log4j/
> >
> > This job will scan both the master and release-2.x branches to build
> > Jenkinsfile pipelines. I'll copy over the Jenkinsfile to release-2.x
> > after confirming it works properly with master. I'm working on getting
> > the various reports generated into Jenkins as well.
> >
> > For testing PRs, we can continue to use Travis (or GitHub Actions) to
> > avoid capacity issues on Jenkins.
> >
> > --
> > Matt Sicker <boa...@gmail.com>
>
>
>
> --
> Matt Sicker <boa...@gmail.com>



-- 
Matt Sicker <boa...@gmail.com>

Reply via email to