> On Apr 5, 2020, at 9:11 AM, Matt Sicker wrote:
>
> Seems like a bug in the config. I don’t think a DOAP file or a Jira report
> needs to be generated for every module in the project. That seems to add a
> lot of network calls which takes a bit of time.
>
True, and we don’t actually publish
Seems like a bug in the config. I don’t think a DOAP file or a Jira report
needs to be generated for every module in the project. That seems to add a
lot of network calls which takes a bit of time.
On Sun, Apr 5, 2020 at 00:36 Ralph Goers wrote:
>
>
> > On Apr 4, 2020, at 10:46 AM, Matt Sicker
> On Apr 4, 2020, at 10:46 AM, Matt Sicker 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
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
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
craz
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
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 wrote:
>
> I've deleted some old pipelines in Jenkins and am updating the one in
> maste
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 Jenkinsfi
