[jira] [Updated] (LOG4J2-1966) Include separator option of PatternLayout in manual

[ https://issues.apache.org/jira/browse/LOG4J2-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Sazzadul Hoque updated LOG4J2-1966: - Description: Url: [https://logging.apache.org/log4j/2.x/manual/layouts.html] In Layouts

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #22

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Obtained Jenkinsfile from 398e16e50affecb1459a812a91e53b5f

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #21

See -- [...truncated 790.77 KB...] Setting up libmono-system-servicemodel-activation4.0-cil (3.2.8+dfsg-10) ... Setting up libmono-system-dynamic4.0-cil (3.2.8+d

Re: [log4net] automated builds and some fresh air for the project

This is looking fantastic! On 3 July 2017 at 08:43, Dominik Psenner wrote: > Hi, > > this is a short heads up about the heavy lifting I'm currently doing win > the CI/CD area. For who does not want to read about this and wants to see > it in action, jump over here and have a look: > > https://bu

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #20

See -- [...truncated 97.99 KB...] [exec] [INFO] configuring report plugin org.apache.maven.plugins:maven-project-info-reports-plugin:2.8.1 [exec] [INF

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #16

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Obtained Jenkinsfile from e29092f8b95f13c10aab6e0c6154a51c

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #13

See -- [...truncated 80.52 KB...] [exec] [INFO] [exec] [INFO] Building Apache

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #12

See -- [...truncated 80.76 KB...] [exec] [INFO] [exec] [INFO] --- maven-site-plugin:3.4:site (default-cli) @ apache-log4net --- [exec] [INFO] co

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #11

See -- [...truncated 793.41 KB...] [exec] [INFO] [exec] [INFO] [exec] [

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #10

See -- [...truncated 15.94 KB...] check-build-defines: set-net-4.0-cp-runtime-configuration: check-log4net-basedir: check-current-bin-dir: clean-curren

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #9

See -- [...truncated 15.93 KB...] check-build-debug: check-build-defines: set-net-4.0-cp-runtime-configuration: check-log4net-basedir: check-current-bin-d

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #8

See -- [...truncated 83.76 KB...] [exec] [INFO] [exec] [INFO] [exec] [IN

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #3

See -- [...truncated 269.43 KB...] aspell-autobuildhash: processing: en [en_CA-variant_0]. aspell-autobuildhash: processing: en [en_CA-variant_1]. aspell-autobuil

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #2

See -- [...truncated 15.22 KB...] check-build-defines: set-net-4.0-cp-runtime-configuration: check-log4net-basedir: check-current-bin-dir: [mkdir] Crea

[jira] [Commented] (LOG4J2-1933) Not able to init config with JsonConfiguration class while the json config nodes are in random order

[ https://issues.apache.org/jira/browse/LOG4J2-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072593#comment-16072593 ] Gary Gregory commented on LOG4J2-1933: -- You can either use a GitHub PR or a attach a

[jira] [Commented] (LOG4J2-1949) On failover from JDBC appender, contents of buffer are not written to failover appender

[ https://issues.apache.org/jira/browse/LOG4J2-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072517#comment-16072517 ] Chris Slater commented on LOG4J2-1949: -- [~garydgregory] Attached is a patch for LOG4

[jira] [Updated] (LOG4J2-1949) On failover from JDBC appender, contents of buffer are not written to failover appender

[ https://issues.apache.org/jira/browse/LOG4J2-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Slater updated LOG4J2-1949: - Attachment: LOG4J2-1949_LOG4J2-1951.patch git patch for LOG4J2-1949 and LOG4J2-1951 > On failove

[log4net] automated builds and some fresh air for the project

Hi, this is a short heads up about the heavy lifting I'm currently doing win the CI/CD area. For who does not want to read about this and wants to see it in action, jump over here and have a look: https://builds.apache.org/blue/organizations/jenkins/logging-log4net/detail/develop/12/pipeline Jen

Build failed in Jenkins: logging-log4net » PR-3 #6

See -- [...truncated 18.56 KB...] set-net-4.0-cp-runtime-configuration: check-log4net-basedir: check-current-bin-dir: clean-current-bin-dir: [echo] Cleaning the bin/net-

Build failed in Jenkins: logging-log4net » PR-1 #6

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Checking out git https://github.com/apache/logging-log4net.git https://github.

Build failed in Jenkins: logging-log4net » PR-4 #6

See -- [...truncated 16.20 KB...] set-net-4.0-cp-runtime-configuration: check-log4net-basedir: check-current-bin-dir: clean-current-bin-dir: [echo] Cleaning the bin/net

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

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Checking out git https://github.com/apache/logging-log4net.git https://github.

Build failed in Jenkins: logging-log4net » feature/Build-mono-on-ubuntu #36

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Obtained Jenkinsfile from b3cb9cb9b5ca5007a827747

Build failed in Jenkins: logging-log4net » feature/Build-mono-on-ubuntu #35

See -- [...truncated 58.33 KB...] check-log4net-basedir: check-current-bin-dir: clean-current-bin-dir: [echo] Cleaning the bin/mono/4.0/debug

Build failed in Jenkins: logging-log4net » feature/Build-mono-on-ubuntu #26

See -- [...truncated 24.28 KB...] + docker inspect -f . dde6c9468b397bf085372bdf18ea003a953eba20 . [Pipeline] withDockerContainer beam5 does not seem to

Build failed in Jenkins: logging-log4net » PR-4 #5

See -- [...truncated 669.16 KB...] [csc] /home/jenkins/jenkins-slave/workspace/logging-log4net_PR-4-VR24Y6RFSBNNVLLELOE2SB5LJDPNOW35DYBTXEVDF6VQMEICHXEA/src/Config/XmlConfigur

Build failed in Jenkins: logging-log4net » PR-8 #5

See -- [...truncated 668.20 KB...] check-sdkdoc-debug: check-current-build-config: check-build-debug: check-build-defines: set-mono-4.0-runtime-configuration: check-log4net

Build failed in Jenkins: logging-log4net » PR-3 #5

See -- [...truncated 221.79 KB...] Certificate added: C=HU, L=Budapest, O=NetLock Halozatbiztonsagi Kft., OU=Tanusitvanykiadok, CN=NetLock Minositett Kozjegyzoi (Class QA) Tanusitv

Build failed in Jenkins: logging-log4net » PR-1 #5

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Checking out git https://github.com/apache/logging-log4net.git https://github.

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

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Checking out git https://github.com/apache/logging-log4net.git https://github.

[jira] [Updated] (LOG4J2-1966) Include separator option of PatternLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Sazzadul Hoque updated LOG4J2-1966: - Summary: Include separator option of PatternLayout (was: Include separator of PatternLay

[jira] [Commented] (LOG4J2-1964) dynamic configuration does not work for filePattern of RollingFile

[ https://issues.apache.org/jira/browse/LOG4J2-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072181#comment-16072181 ] Pierrick HYMBERT commented on LOG4J2-1964: -- Please see submitted PR into LOG4J2-

[jira] [Updated] (LOG4J2-1966) Include separator of PatternLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Sazzadul Hoque updated LOG4J2-1966: - Description: Url: [https://logging.apache.org/log4j/2.x/manual/layouts.html] In Layouts

[jira] [Updated] (LOG4J2-1966) Include separator of PatternLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Sazzadul Hoque updated LOG4J2-1966: - Description: Url: [https://logging.apache.org/log4j/2.x/manual/layouts.html] In Layouts

[jira] [Closed] (LOG4J2-1965) logger filter cant work

[ https://issues.apache.org/jira/browse/LOG4J2-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] thomas.zheng closed LOG4J2-1965. Resolution: Fixed logger filter will be applied after.. > logger filter cant work > --

[jira] [Created] (LOG4J2-1966) Include separator of PatternLayout

M Sazzadul Hoque created LOG4J2-1966: Summary: Include separator of PatternLayout Key: LOG4J2-1966 URL: https://issues.apache.org/jira/browse/LOG4J2-1966 Project: Log4j 2 Issue Type: Docu

Jenkins build is back to normal : log4net-trunk-tests #100

See

Build failed in Jenkins: logging-log4net » feature/Build-mono-on-ubuntu #18

See -- [...truncated 442.64 KB...] done. Setting up mono-complete (4.2.1.102+dfsg2-7ubuntu4) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... Pr

[jira] [Commented] (LOG4J2-1933) Not able to init config with JsonConfiguration class while the json config nodes are in random order

[ https://issues.apache.org/jira/browse/LOG4J2-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072142#comment-16072142 ] Roman Sosnin commented on LOG4J2-1933: -- Hi Gary, Sorry, I don't understand where &

Build failed in Jenkins: log4net-trunk-tests #99

See Changes: [dpsenner] builder-mono-3.5: fixed yet another typo -- Started by upstream project "log4net-trunk-build" build number 229 originally caused by: Started by a

Build failed in Jenkins: log4net-trunk-tests #98

See Changes: [dpsenner] Jenkinsfile: fixed typos -- Started by upstream project "log4net-trunk-build" build number 228 originally caused by: Started by an SCM change [En

Build failed in Jenkins: logging-log4net » feature/Build-mono-on-ubuntu #17

See -- [...truncated 13.38 KB...] > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from 2 remote Git repositories > git config remo

Build failed in Jenkins: logging-log4net » feature/Build-mono-on-ubuntu #16

See -- [...truncated 8.50 KB...] [Pipeline] bat [eature_Build-mono-on-ubuntu-ZF5F7EYV3VT6KMB3FXXJSQSWD62CLIIE54RB46S7P3UAUYBXLPBQ] Running batch script

Build failed in Jenkins: log4net-trunk-tests #97

See Changes: [dpsenner] builder-mono-2.0: removed timezone hack -- Started by upstream project "log4net-trunk-build" build number 227 originally caused by: Started by an

Build failed in Jenkins: log4net-trunk-tests #96

See Changes: [dpsenner] Jenkinsfile: mount localtime into the docker containers -- Started by upstream project "log4net-trunk-build" build number 226 originally caused by

Build failed in Jenkins: logging-log4net » feature/Build-mono-on-ubuntu #15

See -- [...truncated 1.98 KB...] > git config remote.origin1.url https://github.com/apache/logging-log4net.git > # timeout=10 Fetching upstream chang

Re: [log4net] set up basic multibranch and pull requests build

On 2017-07-02, Dominik Psenner wrote: > After a little investigation I found out that are going to have trouble > with building mono assemblies that target mono1.0, mono-2.0, mono-4.0 with > a recent installation of mono-4.5: > http://www.mono-project.com/docs/about-mono/releases/4.0.0/#dropped-s

Re: [log4net] set up basic multibranch and pull requests build

Hi Dominik I hope you'll be getting better soon, even though it would probably mean you'll have to slow down. On 2017-07-01, Dominik Psenner wrote: > An idea crossed my mind. Couldn't we build the Mono binaries on the ubuntu > machines? .net core should build both on ubuntu and on windows. nant

Build failed in Jenkins: logging-log4net » feature/Build-mono-on-ubuntu #14

See -- [...truncated 1.98 KB...] > git config remote.origin1.url https://github.com/apache/logging-log4net.git > # timeout=10 Fetching upstream chang

Build failed in Jenkins: log4net-trunk-tests #95

See Changes: [dpsenner] builder-mono-2.0: set up utc timezone -- Started by upstream project "log4net-trunk-build" build number 225 originally caused by: Started by an S

Re: Build failed in Jenkins: logging-log4net » feature/Build-mono-on-ubuntu #13

Am I the only one bothered by this Jenkins failure message? In the past couple of days, I’ve received over 50+ messages of the same. Anyone responsible for this can take necessary action to stop this spamming the mailbox? thanks, Chandra On 3 Jul 2017, 2:01 PM +0530, Apache Jenkins Server , wr

Build failed in Jenkins: logging-log4net » feature/Build-mono-on-ubuntu #13

See -- [...truncated 203.42 KB...] Certificate added: O=Digital Signature Trust Co., CN=DST Root CA X3 Certificate added: C=DE, O=Deutsche Telekom AG, O

Build failed in Jenkins: log4net-trunk-tests #94

See Changes: [dpsenner] builder-mono-2.0: base it on ubuntu [dpsenner] builder-mono-3.5: base it on ubuntu:latest [dpsenner] builder-mono-4.0: base it on ubuntu and include reference assemblies --

Build failed in Jenkins: logging-log4net » feature/Build-mono-on-ubuntu #12

See -- [...truncated 5.35 KB...] [Pipeline] // stage [Pipeline] withEnv [Pipeline] { [Pipeline] stage [Pipeline] { (Checkout) [Pipeline] checkout > git

Build failed in Jenkins: log4net-trunk-tests #93

See Changes: [dpsenner] NAnt: added mono-4.5 build configuration [dpsenner] Refactored targets to allow building debug and release configurations of [dpsenner] Added dockers for mono 2.0, 3.5 and 4.0 and refa

Jenkins build is back to normal : log4net-trunk-build #223

See

Build failed in Jenkins: logging-log4net » feature/Build-mono-on-ubuntu #11

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Obtained Jenkinsfile from f211495f423da71e98827b6

Build failed in Jenkins: log4net-trunk-build #222

See Changes: [dpsenner] Jenkinsfile: renamed stages -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-1 (Wi

Build failed in Jenkins: log4net-trunk-build #221

See Changes: [dpsenner] Jenkinsfile: build net-4.0 only on windows -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on win

Build failed in Jenkins: logging-log4net » feature/Build-mono-on-ubuntu #10

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Obtained Jenkinsfile from 043bc612d1500b63aea3919

Build failed in Jenkins: log4net-trunk-build #220

See Changes: [dpsenner] NAnt: added mono-4.5 build configuration [dpsenner] Refactored targets to allow building debug and release configurations of [dpsenner] Added dockers for mono 2.0, 3.5 and 4.0 and ref