Re: [Log4j] Updating Jenkins pipelines

> 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

Re: [VOTE] Log4Net dormant release

+1 Remko. > On Apr 5, 2020, at 8:50, Ralph Goers wrote: > > +1 > > Ralph > >> On Apr 4, 2020, at 3:24 PM, Ralph Goers wrote: >> >> I have modified the STATUS.txt and README.txt for Log4Net, tagged the >> source, zipped it and then published it to >> https://dist.apache.org/repos/dist/de

Log4Net

The steps to mark Log4jNet as inactive were: 1. Create a tag of the source. 2. Create an archive of the source to be placed in the logging distribution directory. 3. Modify the Log4Net web site to indicate it is dormant. 4. Modify the web site to include Log4Net in a list of dormant projects alo

Re: svn commit: r1058827 - /websites/production/logging/content/log4net/log4net-2.0.8/index.html

Email dev-unsubscr...@logging.apache.org to unsubscribe. On Sat, 4 Apr 2020 at 19:19, Harry Martyrossian wrote: > > Dear all: > > Will you please let me know how to opt-out from emails? > > Thank you, > Harry > > -Original Message- > From: rgo...@apache.org > Sent: Saturday, April 4, 202

RE: svn commit: r1058827 - /websites/production/logging/content/log4net/log4net-2.0.8/index.html

Dear all: Will you please let me know how to opt-out from emails? Thank you, Harry -Original Message- From: rgo...@apache.org Sent: Saturday, April 4, 2020 5:16 PM To: comm...@logging.apache.org Subject: svn commit: r1058827 - /websites/production/logging/content/log4net/log4net-2.0.8

Re: [VOTE] Log4Net dormant release

+1 Ralph > On Apr 4, 2020, at 3:24 PM, Ralph Goers wrote: > > I have modified the STATUS.txt and README.txt for Log4Net, tagged the source, > zipped it and then published it to > https://dist.apache.org/repos/dist/dev/logging/log4net/ >

Build failed in Jenkins: logging-log4net » PR-54 #2

See Changes: -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Loading trusted files from base branch master at 644cfa1ba879fb41f

Build failed in Jenkins: logging-log4net » PR-43 #2

See Changes: -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Loading trusted files from base branch master at 644cfa1ba879fb41f

Build failed in Jenkins: logging-log4net » PR-51 #7

See Changes: -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Loading trusted files from base branch master at 644cfa1ba879fb41f

Build failed in Jenkins: logging-log4net » PR-24 #2

See Changes: -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Loading trusted files from base branch master at 644cfa1ba879fb41f

Build failed in Jenkins: logging-log4net » PR-53 #2

See Changes: -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Loading trusted files from base branch master at 644cfa1ba879fb41f

Build failed in Jenkins: logging-log4net » PR-56 #2

See Changes: -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Loading trusted files from base branch master at 644cfa1ba879fb41f

Build failed in Jenkins: logging-log4net » PR-57 #2

See Changes: -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Loading trusted files from base branch master at 644cfa1ba879fb41f

[VOTE] Log4Net dormant release

I have modified the STATUS.txt and README.txt for Log4Net, tagged the source, zipped it and then published it to https://dist.apache.org/repos/dist/dev/logging/log4net/ . This is a vote to move those artifacts to the distribution release

Re: [Log4j] Updating Jenkins pipelines

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

Re: [Log4j] Updating Jenkins pipelines

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

Re: [Log4j] Updating Jenkins pipelines

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