Looking more closely at how the ASF Jenkins is set up, here are some nice findings:
* Every Jenkins node comes with an .m2/settings.xml and .m2/toolchains.xml which have snapshot publishing and all versions of java defined respectively. * Email and Slack are already pre-configured to just send out notifications as necessary. I'm running the pipeline now, though I think this should work. It's updated to deploy snapshots again, and it will notify both the notifications list and Slack for various build events (I've made the email one slightly less spammy than before, though the "unstable" build results are only being sent to Slack for now). Once I've confirmed it's working in master, I'll backport the updates to release-2.x again to finish this. On Sat, 4 Apr 2020 at 12:46, Matt Sicker <boa...@gmail.com> wrote: > > I almost forgot: I still need to re-enable snapshot deployments. I'll > do that today. > > The nice advantage to this updated build is that we can start tracking > some of the quality metrics we've configured in the build. While most > of these metrics get published in the generated site (which takes a > crazy amount of time to generate at the moment I noticed: about 30 > minutes on Jenkins), we don't do anything with them. While Commons is > using some SaaS tooling for this (code coverage checks, etc.), we > could work toward something similar. This may also help us figure out > which of the various static analysis settings can be enabled or > disabled (e.g., some of the error-prone warnings in the logs involve > abusing a generic return type for erasure-based type casting; while > this is indeed typically a bad idea, it's impossible to avoid in a > dynamic framework like log4j-core without language support for macros > and a stronger runtime type system). This could also form a nice basis > for a collection of easy first-timer issues to clean up and get new > contributors! > > On Sat, 4 Apr 2020 at 02:31, Matt Sicker <boa...@gmail.com> wrote: > > > > 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> > > > > -- > Matt Sicker <boa...@gmail.com> -- Matt Sicker <boa...@gmail.com>
