See
<https://builds.apache.org/job/logging-log4net/job/feature%252FBuild-mono-on-ubuntu/10/display/redirect>
--
Branch indexing
Connecting to https://api.github.com using dpsenner/** (dpsenner at github)
Obtained Jenkinsfil
See
<https://builds.apache.org/job/log4net-trunk-build/220/display/redirect?page=changes>
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
See
<https://builds.apache.org/job/logging-log4net/job/feature%252FBuild-mono-on-ubuntu/9/display/redirect>
--
[...truncated 17.03 KB...]
[csc] Compiling 227 files to
'f:\jenkins\jenkins-slave\workspace\eature_Build-mon
See
<https://builds.apache.org/job/logging-log4net/job/feature%252FBuild-mono-on-ubuntu/8/display/redirect>
--
[...truncated 19.27 KB...]
compile-mono-1.0:
[echo] Skipping build; required framework is not available: Mono 1.0
compile-mo
See
<https://builds.apache.org/job/logging-log4net/job/feature%252FBuild-mono-on-ubuntu/7/display/redirect>
--
[...truncated 14.96 KB...]
[exec] 'dotnet' failed to start.
[echo] Skipping build; required framework is not availa
I was about to suggest docker images for supporting older versions. I'm
somewhat surprised that Apache Infra hasn't jumped on the bandwagon already
and started "virtualizing" each version of Java and other things into
docker images. It's been the easiest way to support heterogeneous build
servers i
See
<https://builds.apache.org/job/logging-log4net/job/feature%252FBuild-mono-on-ubuntu/5/display/redirect>
--
[...truncated 15.34 KB...]
compile-netcf-1.0:
[echo] Skipping build; required framework is not available: .NET Compact
Framewo
See
<https://builds.apache.org/job/log4net-trunk-build/215/display/redirect?page=changes>
See
<https://builds.apache.org/job/logging-log4net/job/feature%252FBuild-mono-on-ubuntu/4/display/redirect>
--
[...truncated 15.42 KB...]
compile-netcf-1.0:
[echo] Skipping build; required framework is not available: .NET Compact
Framewo
See
<https://builds.apache.org/job/log4net-trunk-build/214/display/redirect?page=changes>
Changes:
[dpsenner] Jenkinsfile: attempt to run apt-get install -y nant
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Bu
See
<https://builds.apache.org/job/logging-log4net/job/feature%252FBuild-mono-on-ubuntu/3/display/redirect>
--
[...truncated 15.67 KB...]
[echo] Skipping build; required framework is not available: .NET Framework
1.0
compile-cli-1.0:
See
<https://builds.apache.org/job/log4net-trunk-build/213/display/redirect?page=changes>
Changes:
[dpsenner] Jenkinsfile: attempt to install nant and run the nant build script
--
Started by an SCM change
[EnvInject] - Loading node environment var
See <https://builds.apache.org/job/log4net-trunk-tests/86/display/redirect>
See
<https://builds.apache.org/job/log4net-trunk-tests/85/display/redirect?page=changes>
Changes:
[dpsenner] Refactored jenkinsfile
[dpsenner] Added a few more usecases to the jenkinsfile
[dpsenner] Fixed jenkinsfile syntax error
[dpsenner] Fixed typo
[dpsenner] Added agent any at pip
See <https://builds.apache.org/job/log4net-trunk-build/211/display/redirect>
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-support-for-old-frameworks
Further, nant does n
fail quietly?
On 2 Jul 2017 12:53 a.m., "Apache Jenkins Server"
wrote:
See <https://builds.apache.org/job/logging-log4net/job/feature%
252FRollingFileAppender-NG/4/display/redirect>
--
Branch indexing
Connecting to https://api.github.co
See
<https://builds.apache.org/job/logging-log4net/job/feature%252FRollingFileAppender-NG/4/display/redirect>
--
Branch indexing
Connecting to https://api.github.com using dpsenner/** (dpsenner at github)
Obtained Jenkinsfil
See <https://builds.apache.org/job/logging-log4net/job/PR-1/4/display/redirect>
--
[...truncated 566 B...]
Fetching upstream changes from https://github.com/apache/logging-log4net.git
> git --version # timeout=10
using GIT_ASKPASS to set cr
See <https://builds.apache.org/job/logging-log4net/job/PR-2/4/display/redirect>
--
[...truncated 1.76 KB...]
> git rev-list 28f46610fc8b42f7bd4d93a85916164210a5bd24 # timeout=10
[Pipeline] node
Still waiting to schedule task
Waiting for next
See <https://builds.apache.org/job/logging-log4net/job/PR-4/4/display/redirect>
--
[...truncated 19.28 KB...]
check-sdkdoc-debug:
check-current-build-config:
check-build-debug:
check-build-defines:
set-net-4.5-runtime-configuration:
check-l
See
<https://builds.apache.org/job/log4net-trunk-build/210/display/redirect?page=changes>
Changes:
[dpsenner] Refactored jenkinsfile
[dpsenner] Added a few more usecases to the jenkinsfile
[dpsenner] Fixed jenkinsfile syntax error
[dpsenner] Fixed typo
[dpsenner] Added agent
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 is
available also for ubuntu and a perfect candidate for a build tool. It
would be even nicer if we could simply add mono as a dependency (i.e.
nuget) and
/logging-log4net/job/develop/
Unfortunately only a subset of all targets are being built:
[echo] The .NET Framework 1.0 is not available. Build skipped.
[echo] The .NET Framework 1.1 is not available. Build skipped.
[echo] The .NET Framework 2.0 is not available. Build skipped
Sounds like a plan that is fine with me given that this is just a minor
change.
2017-07-01 18:22 GMT+02:00 Stefan Bodewig :
> On 2017-06-30, Dominik Psenner wrote:
>
> > While working on the Jenkinsfile so that jjenkins builds all kinds of
> > branches for us I noticed that pr-11 made it into mas
On 2017-06-30, Dominik Psenner wrote:
> While working on the Jenkinsfile so that jjenkins builds all kinds of
> branches for us I noticed that pr-11 made it into master without us carving
> out a release.
It's been my fault. I committed it to master out of habit and merged it
to develop later whe
See <https://builds.apache.org/job/log4net-trunk-tests/82/display/redirect>
See
<https://builds.apache.org/job/log4net-trunk-tests/81/display/redirect?page=changes>
Changes:
[bodewig] (doc) Fix name of class LogicalThreadContext
[dpsenner] Added a first jenkinsfile that does echo on a windows node.
[dpsenner] Changed node to windows-2012-2
[dpsenner] Changed
See <https://builds.apache.org/job/log4net-trunk-build/207/display/redirect>
See
<https://builds.apache.org/job/log4net-trunk-build/206/display/redirect?page=changes>
Changes:
[bodewig] (doc) Fix name of class LogicalThreadContext
[dpsenner] Added a first jenkinsfile that does echo on a windows node.
[dpsenner] Changed node to windows-2012-2
[dpsenner] Changed
Hi
While working on the Jenkinsfile so that jjenkins builds all kinds of
branches for us I noticed that pr-11 made it into master without us carving
out a release. The change is no big deal and I just pushed changes to
master too in order to have jenkins build that branch for us. Is this
change in
Hi,
I am currently tied to my bed and used that spare time to set up basic
multibranch and pull request builds that fly in from github.
https://builds.apache.org/job/logging-log4net/
respectively this page:
https://builds.apache.org/blue/organizations/jenkins/logging-log4net
Tests and build
Github user dpsenner commented on the issue:
https://github.com/apache/logging-log4net/pull/12
Merged with develop.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user asfgit closed the pull request at:
https://github.com/apache/logging-log4net/pull/12
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
GitHub user dpsenner opened a pull request:
https://github.com/apache/logging-log4net/pull/12
This is a test whether builds.a.o picks up this pull request
Ideally, this build should show up at
https://builds.apache.org/blue/organizations/jenkins/logging-log4net/pr
You can merge
See <https://builds.apache.org/job/log4net-trunk-tests/75/display/redirect>
See <https://builds.apache.org/job/log4net-trunk-build/201/display/redirect>
See <https://builds.apache.org/job/log4net-trunk-tests/74/display/redirect>
--
[...truncated 643 B...]
Started by an SCM change
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-2 (Windo
See <https://builds.apache.org/job/log4net-trunk-build/200/display/redirect>
--
Started by an SCM change
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-1 (Windows) in workspace
See <https://builds.apache.org/job/log4net-trunk-tests/73/display/redirect>
--
[...truncated 32.59 KB...]
[nunit2] 11)
log4net.Tests.Appender.RollingFileAppenderTest.TestInterProcessLockUnlocks :
log4net.Core.LogException : Repository [TestRepo
See <https://builds.apache.org/job/log4net-trunk-tests/72/display/redirect>
--
[...truncated 643 B...]
Started by an SCM change
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-2 (Windo
See <https://builds.apache.org/job/log4net-trunk-tests/71/display/redirect>
--
[...truncated 3.73 KB...]
http://nant.sourceforge.net
Buildfile:
file:///f:/jenkins/jenkins-slave/workspace/log4net-trunk-tests/log4net.build
Target framework: Microsof
See <https://builds.apache.org/job/log4net-trunk-tests/70/display/redirect>
--
Started by upstream project "log4net-trunk-build" build number 196
originally caused by:
Started by an SCM change
Started by an SCM change
[EnvInject] - Loading
See <https://builds.apache.org/job/log4net-trunk-tests/69/display/redirect>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-2 (Windows) in workspace
<https://builds.apache.org/jo
See <https://builds.apache.org/job/log4net-trunk-tests/68/display/redirect>
--
Started by an SCM change
Started by upstream project "log4net-trunk-build" build number 195
originally caused by:
Started by an SCM change
[EnvInject] - Loading
See <https://builds.apache.org/job/log4net-trunk-tests/67/display/redirect>
--
Started by an SCM change
Started by upstream project "log4net-trunk-build" build number 194
originally caused by:
Started by an SCM change
[EnvInject] - Loading
See <https://builds.apache.org/job/log4net-trunk-build/194/display/redirect>
See <https://builds.apache.org/job/log4net-trunk-build/193/display/redirect>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-3 (Windows) in workspace
<https://builds.apache.org/jo
See <https://builds.apache.org/job/log4net-trunk-build/192/display/redirect>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-3 (Windows) in workspace
<https://builds.apache.org/jo
See <https://builds.apache.org/job/log4net-trunk-tests/64/display/redirect>
See <https://builds.apache.org/job/log4net-trunk-build/190/display/redirect>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-3 (Windows) in workspace
<https://builds.apache.org/jo
See <https://builds.apache.org/job/log4net-trunk-tests/63/display/redirect>
--
[...truncated 643 B...]
Started by an SCM change
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-2 (Windo
See <https://builds.apache.org/job/log4net-trunk-build/191/display/redirect>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-3 (Windows) in workspace
<https://builds.apache.org/jo
See <https://builds.apache.org/job/log4net-trunk-tests/62/display/redirect>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-2 (Windows) in workspace
<https://builds.apache.org/jo
See <https://builds.apache.org/job/log4net-trunk-tests/61/display/redirect>
--
Started by upstream project "log4net-trunk-build" build number 186
originally caused by:
Started by an SCM change
Started by an SCM change
Started by upstream
See <https://builds.apache.org/job/log4net-trunk-build/185/display/redirect>
See <https://builds.apache.org/job/log4net-trunk-build/184/display/redirect>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-3 (Windows) in workspace
<https://builds.apache.org/jo
See <https://builds.apache.org/job/log4net-trunk-tests/56/display/redirect>
--
[...truncated 643 B...]
Started by an SCM change
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-2 (Windo
See <https://builds.apache.org/job/log4net-trunk-tests/57/display/redirect>
See <https://builds.apache.org/job/log4net-trunk-tests/55/display/redirect>
--
[...truncated 2.09 KB...]
> git rev-parse "refs/tags/rel/1.2.9^{commit}" # timeout=10
> git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # t
See <https://builds.apache.org/job/log4net-trunk-tests/54/display/redirect>
--
Started by upstream project "log4net-trunk-build" build number 179
originally caused by:
Started by an SCM change
Started by an SCM change
[EnvInject] - Loading
See <https://builds.apache.org/job/log4net-trunk-tests/53/display/redirect>
--
Started by upstream project "log4net-trunk-build" build number 178
originally caused by:
Started by an SCM change
[EnvInject] - Loading node environment var
See <https://builds.apache.org/job/log4net-trunk-build/178/display/redirect>
See <https://builds.apache.org/job/log4net-trunk-build/177/display/redirect>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-3 (Windows) in workspace
<https://builds.apache.org/jo
See <https://builds.apache.org/job/log4net-trunk-build/176/display/redirect>
--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-3 (Windows) in workspace
<https://builds.apache.org/jo
Argh, I pushed this to the wrong branch (master instead of develop) by
habit.
Sorry
Stefan
Github user asfgit closed the pull request at:
https://github.com/apache/logging-log4net/pull/11
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user bodewig commented on the issue:
https://github.com/apache/logging-log4net/pull/11
merged, many thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
GitHub user MarcelGosselin opened a pull request:
https://github.com/apache/logging-log4net/pull/11
(doc) Fix name of class LogicalThreadContext
Fix name of class LogicalThreadContext in Scopes section, words were
reversed.
You can merge this pull request into a Git repository by
Github user zippy1981 commented on the issue:
https://github.com/apache/logging-log4net/pull/2
@dpsenner Waiting for your response to my comments.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
like to update the build configuration on builds.apache.org
so that log4net is built with pipelines against multiple branches and pull
requests. Would you please grant me the karma to work on this?
Cheers,
Dominik
2017-06-13 0:14 GMT+02:00 Dominik Psenner :
Hi Ralph,
would you please grant me kar
Hi Dominik
you should be set now, I've used my Gump PMC chairman powers and added
you to the LDAP group for Jenkins admins.
Stefan
On 2017-06-22, Dominik Psenner wrote:
> *bump*
> I would still like to update the build configuration on builds.apache.org
> so that log4net
Github user dpsenner commented on the issue:
https://github.com/apache/logging-log4net/pull/6
This patch provides the same functionality as #9 does. Since this patch
affects the current behavior and I have a bad feeling about changing the
behavior of the rolling file appender, I see
Github user dpsenner commented on the issue:
https://github.com/apache/logging-log4net/pull/10
The patch basically wraps the invocation to WindowsIdentity.GetCurrent()
into a provider that refreshes the identity in the background once every 15
seconds. Please discuss!
---
If your
GitHub user dpsenner opened a pull request:
https://github.com/apache/logging-log4net/pull/10
Improve the performance of looking up the windows identity
This reopens the old pull request 45.
You can merge this pull request into a Git repository by running:
$ git pull https
Github user dpsenner commented on the issue:
https://github.com/apache/logging-log4net/pull/9
With respect to #6 this patch is cleaner. Since this affects the current
behavior and I have a bad feeling about changing the behavior of the rolling
file appender, I see a unit test as a
GitHub user dpsenner opened a pull request:
https://github.com/apache/logging-log4net/pull/9
Allow for dates that aren't necessarily in the -MM-dd format.
This reopens the old pull request 43. Please note that the old pull request
29 (reopened as #6) provides the
Github user dpsenner commented on the issue:
https://github.com/apache/logging-log4net/pull/8
This is again a rather large patch that requires an ICLA from the original
author Harry Martyrossian.
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user dpsenner opened a pull request:
https://github.com/apache/logging-log4net/pull/8
Implemented changes for the Util/AppenderAttachedImpl.cs class for calling
log4net appenders in parallel using .NET Task Parallel Library
This reopens the old pull request 40 and provides a
Github user dpsenner commented on the issue:
https://github.com/apache/logging-log4net/pull/7
We need an ICLA from the author Peter Jas since this is a rather large
change.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
GitHub user dpsenner opened a pull request:
https://github.com/apache/logging-log4net/pull/7
Add log4net asp.net extension
This reopens the old pull request 32 and provides a place for discussion.
It would be nice to have some feedback from the author of the original patch.
You
GitHub user dpsenner opened a pull request:
https://github.com/apache/logging-log4net/pull/6
Try and trap a date when looking for the next backup number.
This reopens the old pull request 29 and provides a place for discussion.
Please note that the old pull request 43 provides the
*bump*
I would still like to update the build configuration on builds.apache.org
so that log4net is built with pipelines against multiple branches and pull
requests. Would you please grant me the karma to work on this?
Cheers,
Dominik
2017-06-13 0:14 GMT+02:00 Dominik Psenner :
> Hi Ra
[
https://issues.apache.org/jira/browse/LOG4NET-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059886#comment-16059886
]
Dominik Psenner commented on LOG4NET-82:
Please note that this is not actuall
[
https://issues.apache.org/jira/browse/LOG4NET-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059275#comment-16059275
]
Ayush Agrawal edited comment on LOG4NET-82 at 6/22/17 12:3
[
https://issues.apache.org/jira/browse/LOG4NET-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059275#comment-16059275
]
Ayush Agrawal commented on LOG4NET-82:
--
I am having a console application where
Ezhumalai created LOG4NET-569:
-
Summary: If I change the name of 'section' name present under
configsections other than "log4net", logging is not happening
Key: LOG4NET-569
URL: https://issues.ap
[
https://issues.apache.org/jira/browse/LOG4NET-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055990#comment-16055990
]
Dominik Psenner commented on LOG4NET-568:
-
Since resolving the identity h
[
https://issues.apache.org/jira/browse/LOG4NET-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055946#comment-16055946
]
Lehel Bara commented on LOG4NET-568:
When you explicitly call the SetThreadPrinc
[
https://issues.apache.org/jira/browse/LOG4NET-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055859#comment-16055859
]
Dominik Psenner commented on LOG4NET-568:
-
If nobody should ac
Lehel Bara created LOG4NET-568:
--
Summary: Would be nice to avoid accessing the
Thread.CurrentPrincipal
Key: LOG4NET-568
URL: https://issues.apache.org/jira/browse/LOG4NET-568
Project: Log4net
Hi Ralph,
would you please grant me karma to add/modify log4net build configurations
on jenkins?
Warm regards
--
Dominik Psenner
In theory, you can use Jenkins pipelines scripts in your projects, but I
haven't tested that out yet. It's the system we're using at my work.
On 12 June 2017 at 14:25, Dominik Psenner wrote:
> I envision to automate the build and publishing process. At work we are
> migrating to git and along wi
I envision to automate the build and publishing process. At work we are
migrating to git and along with that we are going to set up our (insane)
build process with gitlab runners executed by virtualbox executors. See
https://docs.gitlab.com/runner/ and
https://docs.gitlab.com/ee/ci/yaml/README.html
We're doing the same in log4j right now as well. I'd love to figure out a
more fluid way of doing this eventually.
On 12 June 2017 at 10:16, Stefan Bodewig wrote:
> On 2017-06-12, Matt Sicker wrote:
>
> > That's an interesting use case. Are you using gitpubsub instead of
> > svnpubsub for the si
On 2017-06-12, Matt Sicker wrote:
> That's an interesting use case. Are you using gitpubsub instead of
> svnpubsub for the site then?
"mvn site" plus manual copy over to svn plus the logging site's
svnpubsub. Yes, it is painful :-)
Stefan
That's an interesting use case. Are you using gitpubsub instead of
svnpubsub for the site then?
On 10 June 2017 at 12:41, Dominik Psenner wrote:
> We have also the site versioned in the same repository. Updates to the
> website do not necessarily synchronize well with the library releases. So
>
We have also the site versioned in the same repository. Updates to the
website do not necessarily synchronize well with the library releases. So
this is a good example where the master branch is useful to track published
website patches. In a wider sense, updates to the website are one kind of
hot
Agreed. Whenever I've used git-flow in the past, the only reason we had a
develop and master branch was so that it was simpler to write hotfixes
against master later on. We'd delete our release branches after they were
tagged and merged to master&develop, so the only ways to find what's in
producti
I'm unlikely to do development on Log4jnet but I like having 'master'
instead of 'develop' for the reason Julius stated.
Gary
On Fri, Jun 9, 2017 at 9:07 AM, Julius Davies
wrote:
> Hi,
>
> The 'master' branch in the gitflow model is pointless (that state is
> already tracked with the 'release/*
901 - 1000 of 1160 matches
Mail list logo
