Re: I've disabled the Log4j2 Jenkins build for now

Yes, that would be ok. If we ever need to add a Jenkins build again for something, we can find the files in the history. — Matt Sicker > On Jan 30, 2022, at 13:56, Volkan Yazıcı wrote: > > Thanks so much Matt! > I have created LOG4J2-3376 > <https://issues.apache.org/jira/

Re: I've disabled the Log4j2 Jenkins build for now

abled the Jenkins build for Log4j2 as we’re already testing PRs > via GitHub right now. Unless we can use a GitHub Action to publish > snapshots, though, I’ll have to update our Jenkins build to simply do just > that for the master and release-2.x branches. I believe we’ve talked about >

Re: I've disabled the Log4j2 Jenkins build for now

Thanks Matt! Gary On Fri, Jan 28, 2022, 11:31 Matt Sicker wrote: > I’ve disabled the Jenkins build for Log4j2 as we’re already testing PRs > via GitHub right now. Unless we can use a GitHub Action to publish > snapshots, though, I’ll have to update our Jenkins build to simply do ju

I've disabled the Log4j2 Jenkins build for now

I’ve disabled the Jenkins build for Log4j2 as we’re already testing PRs via GitHub right now. Unless we can use a GitHub Action to publish snapshots, though, I’ll have to update our Jenkins build to simply do just that for the master and release-2.x branches. I believe we’ve talked about this

Re: Jenkins build

The Windows build doesn't seem to be the issue. It seems to be related to running mvn deploy for the snapshot. See logs: https://ci-builds.apache.org/job/Logging/job/log4j/job/master/256/console On Mon, 5 Apr 2021 at 16:34, Matt Sicker wrote: > > Alright, the Linux side passed, but the Windows si

Re: Jenkins build

Alright, the Linux side passed, but the Windows side had a module-related import error with OSGi. On Mon, 5 Apr 2021 at 16:21, Matt Sicker wrote: > > I've updated the mvn step to use Java 11 on the master branch. That > will apply to any other pipelines using this at the moment, but that > should

Re: Jenkins build

I've updated the mvn step to use Java 11 on the master branch. That will apply to any other pipelines using this at the moment, but that shouldn't be a problem for now. On Mon, 5 Apr 2021 at 09:30, Matt Sicker wrote: > > Also, Jenkins docs are usually in Jenkins itself like these useful > pages (

Re: Jenkins build

Also, Jenkins docs are usually in Jenkins itself like these useful pages (I reference them every time I need to make non-trivial changes): https://ci-builds.apache.org/job/Logging/job/log4j/pipeline-syntax/ https://ci-builds.apache.org/job/Logging/job/log4j/pipeline-syntax/html (warning: loong

Re: Jenkins build

https://github.com/apache/struts/blob/777caaade067b755b9aa4638f28ba8579d1c7a1d/Jenkinsfile#L32-L34 is the gist of how it's normally supposed to be configured for the sh/bat steps. I'll figure out a specific fix later today. On Sun, 4 Apr 2021 at 23:25, Ralph Goers wrote: > > Yes, I saw the mvn co

Re: Jenkins build

Yes, I saw the mvn command. But I couldn’t figure out what logic to use to get it to only use Java 11 for Log4j master since this seems to be used for multiple builds. I can’t seem to find clear docs on all the variables or methods that are available to use in a groovy script. I admit to being a

Re: Jenkins build

Yeah, I can update it. I used a workaround a while ago with hard coded JDKs which probably has a simpler approach now. The mvn command is in the vars directory. On Sun, Apr 4, 2021 at 21:09 Ralph Goers wrote: > Matt, > > I just noticed that the build for Log4j 2 Master is failing. I guess you >

Jenkins build

Matt, I just noticed that the build for Log4j 2 Master is failing. I guess you must have modified the configuration a while ago. I had thought each project had their own Jenkins file but it appears they are all now sharing one in the logging-pipelines project. I took a look at that project but

Re: Jenkins build failure in JSON template module

Thank you Volkan! :-) Gary On Tue, Nov 17, 2020, 08:12 Volkan Yazıcı wrote: > revapi complaints. Fixed. > > On Mon, Nov 16, 2020 at 4:19 PM Gary Gregory > wrote: > > > Hi All, > > > > The Jenkins build is failing in the JSON template module. > > > > Gary > > >

Re: Jenkins build failure in JSON template module

revapi complaints. Fixed. On Mon, Nov 16, 2020 at 4:19 PM Gary Gregory wrote: > Hi All, > > The Jenkins build is failing in the JSON template module. > > Gary >

Re: Jenkins build failure in JSON template module

Hey Gary, Thanks for the heads-up. I am indeed aware of the break in the build, though still couldn't spare time to take a look. I hope to put it into working state some time tomorrow. Kind regards. On Mon, Nov 16, 2020 at 4:19 PM Gary Gregory wrote: > Hi All, > > The Jenkins bu

Jenkins build failure in JSON template module

Hi All, The Jenkins build is failing in the JSON template module. Gary

Re: [Scala] Jenkins build failure (#1)

Well, that should've been text instead of html. Oops. On Fri, 17 Jul 2020 at 19:07, Mr. Jenkins wrote: > > > BODY, TABLE, TD, TH, P { > font-family: Calibri, Verdana, Helvetica, sans serif; > font-size: 12px; > color: black; > } > .console { > font-family: Courier New; >

Re: Build failure in Jenkins build of log4j/release-2.x (10)

Updated, see build #15 for the latest failure. On Sat, 11 Apr 2020 at 18:37, Matt Sicker wrote: > > Oh I see the issue here. Needs more back ports from master. I’ll update this. > > On Sat, Apr 11, 2020 at 18:25 Ralph Goers wrote: >> >> Why have these builds been failing for the last week? I loo

Re: Build failure in Jenkins build of log4j/release-2.x (14)

I've pushed the backport for fixing this build error. For those curious: the problem was the "recordIssues" build step requires a Jenkins agent to execute, and I had configured the pipeline not to use on at the root level. The mail and slackSend steps are both node-less steps (i.e., they're basical

Re: Build failure in Jenkins build of log4j/release-2.x (10)

Oh I see the issue here. Needs more back ports from master. I’ll update this. On Sat, Apr 11, 2020 at 18:25 Ralph Goers wrote: > Why have these builds been failing for the last week? I looked at it but > whatever is going on is incomprehensible to me. > > Ralph > > > On Apr 11, 2020, at 4:19 PM,

Re: Build failure in Jenkins build of log4j/release-2.x (10)

Why have these builds been failing for the last week? I looked at it but whatever is going on is incomprehensible to me. Ralph > On Apr 11, 2020, at 4:19 PM, Apache Jenkins Server > wrote: > > > There is a build failure in log4j/release-2.x. > > Build: https://builds.apache.org/job/log4j/jo

Re: Jenkins build is still unstable: Log4j 2 2.x #4160

So this looks like a real test failure. It's not happening in the Windows agents, but it's happening in the Ubuntu agents. On Sat, 4 Apr 2020 at 00:35, Apache Jenkins Server wrote: > > See > -- Matt Sicker

Re: Jenkins build is back to stable : Log4j2Windows #62

🎉 On Sun, 23 Feb 2020 at 13:06, Apache Jenkins Server wrote: > > See > > -- Matt Sicker

Re: Jenkins build is back to stable : Log4j 2 3.x #498

Hooray! I think I had pushed one of the previous commits (replace @PluginBuilderFactory with @PluginFactory) without re-running tests. I fixed the ambiguous code left over from that refactoring (mostly in unit tests). I also made sure to try and simplify as many factory methods as I could find init

Re: Jenkins build became unstable: Log4j 2 3.x #497

Pretty sure I ran all the tests before pushing this commit. We'll see how this changes on the next push. On Sun, 6 Oct 2019 at 19:57, Apache Jenkins Server wrote: > > See > > -- Matt Sicker

Re: Jenkins build became unstable: Log4j 2 3.x #476

Just a small inconsistency I found while refactoring. I fixed the issue I caused already. On Sat, Aug 31, 2019 at 23:15, Ralph Goers wrote: > I don’t understand. What is the problem? As you noted it has always been > this way. > > Ralph > > > On Aug 31, 2019, at 9:03 PM, Matt Sicker wrote: > >

Re: Jenkins build became unstable: Log4j 2 3.x #476

I don’t understand. What is the problem? As you noted it has always been this way. Ralph > On Aug 31, 2019, at 9:03 PM, Matt Sicker wrote: > > The plugin category is used to distinguish that in this API, not the class. > It seems as though both use the same interface except for the one class.

Re: Jenkins build became unstable: Log4j 2 3.x #476

The plugin category is used to distinguish that in this API, not the class. It seems as though both use the same interface except for the one class. Generic type erasure avoided this from cropping up before. On Sat, Aug 31, 2019 at 20:50, Ralph Goers wrote: > > Because it isn’t a PatternConverte

Re: Jenkins build became unstable: Log4j 2 3.x #476

Because it isn’t a PatternConverter? Look at what it does. The newInstance method creates a DatePatternConverter. The FileDatePatternConverter and IntegerPatternConverter are both used for the filePattern in the rolling file appender, not for a pattern layout. Ralph > On Aug 31, 2019, at 12

Re: Jenkins build became unstable: Log4j 2 3.x #476

Ah, this is an interesting historical design decision dating back to the very first commit! Why exactly does DatePatternConverter _not_ implement PatternConverter like literally every other converter class does? On Sat, 31 Aug 2019 at 14:29, Matt Sicker wrote: > > Shit, I'm on it. > > On Sat, 31

Re: Jenkins build became unstable: Log4j 2 3.x #476

FileDatePatternConverter, not DatePatternConverter. On Sat, 31 Aug 2019 at 14:35, Matt Sicker wrote: > > Ah, this is an interesting historical design decision dating back to > the very first commit! Why exactly does DatePatternConverter _not_ > implement PatternConverter like literally every othe

Re: Jenkins build became unstable: Log4j 2 3.x #476

Shit, I'm on it. On Sat, 31 Aug 2019 at 13:50, Apache Jenkins Server wrote: > > See > > -- Matt Sicker

Re: Jenkins build is still unstable: Log4j 2 2.x #3757

There are failing commits with the latest timezone fomatting changes. Ralph > On Dec 4, 2018, at 7:37 PM, Apache Jenkins Server > wrote: > > See > > >

Re: Jenkins build became unstable: Log4j 2 2.x #3753

> Date: Sat, Dec 1, 2018 at 3:53 PM > Subject: Jenkins build became unstable: Log4j 2 2.x #3753 > To: > > > See <https://builds.apache.org/job/Log4j%202%202.x/3753/display/redirect>

Fwd: Jenkins build became unstable: Log4j 2 2.x #3753

Is this failure related to the recent file close issue in the tests? Gary -- Forwarded message - From: Apache Jenkins Server Date: Sat, Dec 1, 2018 at 3:53 PM Subject: Jenkins build became unstable: Log4j 2 2.x #3753 To: See <https://builds.apache.org/job/Log4j%202%202.x/3

Re: Jenkins build became unstable: Log4j 2 3.x #18

Strange, master builds fine on my machine. CloseableThreadContextTest also all pass on my machine. On Mon, Feb 26, 2018 at 10:22 PM, Remko Popma wrote: > This is likely my last commit. > I’ll look into this tomorrow. > > > > On Feb 26, 2018, at 21:06, Apache Jenkins Server < > jenk...@builds.

Re: Jenkins build became unstable: Log4j 2 3.x #18

This is likely my last commit. I’ll look into this tomorrow. > On Feb 26, 2018, at 21:06, Apache Jenkins Server > wrote: > > See > >

Re: Jenkins build is still unstable: Log4j 2 3.x #5

This was fixed by updating to the latest plugin version a couple of days ago. Gary On Mon, Feb 19, 2018, 22:29 Gary Gregory wrote: > The MongoDB failures could be > https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo/issues/167 > > I'll take a look tomorrow at some point. > > Gary > >

Re: Jenkins build is still unstable: Log4j 2 3.x #5

The MongoDB failures could be https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo/issues/167 I'll take a look tomorrow at some point. Gary On Mon, Feb 19, 2018 at 8:30 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

Re: Jenkins build is unstable: Log4j 2 3.x #1

I've seen that happen on Windows only, which this is not. On Windows this seems to be a MongoDB packaging bug which surfaces as: https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo/issues/232 and https://jira.mongodb.org/browse/SERVER-32877 But since this is Linux... I'll try the same

Re: Jenkins build is unstable: Log4j 2 3.x #1

The mongo db test failed. Ralph > On Feb 18, 2018, at 12:35 AM, Apache Jenkins Server > wrote: > > See > >

Re: Jenkins build is still unstable: Log4j 2.x #3170

Makes sense, fixed. On 2017-11-18 21:17, Ralph Goers wrote: The file should be deleted before the test starts and after it finishes. If it fails for some reason it will still leave the file lying around so deleting it before the test insures a clean environment.

Re: Jenkins build is still unstable: Log4j 2.x #3170

The file should be deleted before the test starts and after it finishes. If it fails for some reason it will still leave the file lying around so deleting it before the test insures a clean environment. Ralph > On Nov 18, 2017, at 5:00 AM, Mikael Ståldal wrote: > > That particular test create

Re: Jenkins build is still unstable: Log4j 2.x #3170

Nice find! On 18 November 2017 at 08:11, Mikael Ståldal wrote: > It works now! > > > > On 2017-11-18 13:00, Mikael Ståldal wrote: > >> That particular test creates hadoop.log in >> System.getProperty("java.io.tmpdir") >> on purpuse to test system property replacement in configuration files. >>

Re: Jenkins build is still unstable: Log4j 2.x #3170

It works now! On 2017-11-18 13:00, Mikael Ståldal wrote: That particular test creates hadoop.log in System.getProperty("java.io.tmpdir") on purpuse to test system property replacement in configuration files. On most Linux systems (including our Jenkins machine), System.getProperty("java.io.

Re: Jenkins build is still unstable: Log4j 2.x #3170

That particular test creates hadoop.log in System.getProperty("java.io.tmpdir") on purpuse to test system property replacement in configuration files. On most Linux systems (including our Jenkins machine), System.getProperty("java.io.tmpdir") == "/tmp". I tried the test locally on my Linux m

Re: Jenkins build is still unstable: Log4j 2.x #3170

Same problem again in latest build (#3182). On 2017-11-12 23:58, Ralph Goers wrote: I am not sure why this is suddenly failing with a permission denied trying to create /tmp/hadoop.log. But why is it trying to create a file there instead of under the target directory? Ralph On Nov 12, 2017

Re: Jenkins build is still unstable: Log4j 2.x #3170

https://github.com/apache/logging-log4j2/search?utf8=%E2%9C%93&q=hadoop.log&type= I see at least one test that's trying to use the java.io.tmpdir for said file. The only reason why a file named /tmp/hadoop.log couldn't be created would be because it already exists and is owned by a different user

Re: Jenkins build is still unstable: Log4j 2.x #3170

I am not sure why this is suddenly failing with a permission denied trying to create /tmp/hadoop.log. But why is it trying to create a file there instead of under the target directory? Ralph > On Nov 12, 2017, at 2:39 PM, Apache Jenkins Server > wrote: > > See >

Re: Jenkins build is still unstable: Log4j 2.x #3128

This looks like it goes back to before your recent commits. There were some test failure notifications earlier. On 16 October 2017 at 15:02, Mikael Ståldal wrote: > I don't understand why these tests fail: > > org.apache.logging.log4j.core.appender.db.AbstractDatabaseManagerTest.testBuffering02

Re: Jenkins build is still unstable: Log4j 2.x #3128

I don't understand why these tests fail: org.apache.logging.log4j.core.appender.db.AbstractDatabaseManagerTest.testBuffering02 org.apache.logging.log4j.core.appender.db.AbstractDatabaseManagerTest.testBuffering03 org.apache.logging.log4j.core.appender.db.AbstractDatabaseManagerTest.testBuffer

Jenkins build is still unstable: Log4j 2.x #3126

See

Jenkins build became unstable: Log4j 2.x #3125

See

Jenkins build is back to normal : Log4j 2.x #3120

See

Jenkins build is back to normal : Log4j 2.x #3116

See

Jenkins build is back to normal : Log4j 2.x #3112

See

Jenkins build is back to normal : Log4j 2.x #3107

See

Jenkins build is back to stable : Log4j 2.x #3104

See

Jenkins build is unstable: Log4j 2.x #3103

See

Jenkins build is back to normal : Log4j 2.x #3092

See

Jenkins build is back to normal : Log4j 2.x #3086

See

Jenkins build is back to normal : Log4j 2.x #3081

See

Jenkins build is back to stable : Log4j 2.x #3066

See

Jenkins build became unstable: Log4j 2.x #3065

See

Jenkins build is back to stable : Log4j 2.x #3061

See

Jenkins build became unstable: Log4j 2.x #3060

See

Jenkins build is back to normal : Log4j 2.x #3054

See

Jenkins build is back to normal : Log4j 2.x #3044

See

Jenkins build is back to normal : Log4j 2.x #3037

See

Jenkins build is back to normal : Log4j 2.x #3033

See

Jenkins build is back to normal : Log4j 2.x #3031

See

Jenkins build is back to normal : Log4j 2.x #3029

See

Jenkins build is back to normal : Log4j 2.x #3017

See

Jenkins build is back to normal : Log4j 2.x #3002

See

Jenkins build is back to stable : Log4j 2.x #2999

See

Jenkins build became unstable: Log4j 2.x #2998

See

Jenkins build is back to stable : Log4j 2.x #2994

See

Jenkins build became unstable: Log4j 2.x #2993

See

Jenkins build is back to stable : Log4j 2.x #2992

See

Jenkins build became unstable: Log4j 2.x #2991

See

Jenkins build is back to normal : Log4j 2.x #2989

See

Jenkins build is back to normal : Log4j 2.x #2982

See

Re: Jenkins build became unstable: Log4j 2.x #2980

It's from an async test. Could be a timing issue. I'd wait to see if it pops up again. On 14 August 2017 at 15:58, Ralph Goers wrote: > > I don’t recall having seen this error before. Did the latest commit break > something? > > Ralph > > > On Aug 14, 2017, at 1:12 PM, Apache Jenkins Server < >

Re: Jenkins build became unstable: Log4j 2.x #2980

I don’t recall having seen this error before. Did the latest commit break something? Ralph > On Aug 14, 2017, at 1:12 PM, Apache Jenkins Server > wrote: > > See > > >

Jenkins build became unstable: Log4j 2.x #2980

See

Jenkins build is back to stable : Log4j 2.x #2978

See

Jenkins build is still unstable: Log4j 2.x #2977

See

Jenkins build is still unstable: Log4j 2.x #2976

See

Jenkins build is still unstable: Log4j 2.x #2975

See

Jenkins build is still unstable: Log4j 2.x #2974

See

Jenkins build became unstable: Log4j 2.x #2973

See

Jenkins build is back to stable : Log4j 2.x #2970

See

Jenkins build is unstable: Log4j 2.x #2969

See

Jenkins build is still unstable: Log4j 2.x #2965

See

Jenkins build is still unstable: Log4j 2.x #2964

See

Jenkins build is still unstable: Log4j 2.x #2963

See

Jenkins build is still unstable: Log4j 2.x #2962

See

Jenkins build is still unstable: Log4j 2.x #2961

See

Jenkins build is still unstable: Log4j 2.x #2960

See

Jenkins build is still unstable: Log4j 2.x #2959

See

  1   2   >