In theory, yes. Creating a (windows) docker container that provides nant by downloading it from the internet should be straight forward. I pointed out the windows docker option to Chris when he first announced the new windows-2016 nodes. But so far I have only very limited experience with windows docker containers and I am not sure whether we should rather drop the support for ancient frameworks and only target log4net against netstandard-2.0 in the future. This however will drop support for quite a few appenders that are windows specific and again needs a ton of refactoring in the codebase. It resembles much on what was already done with modularizing log4j into api, core etc.

On 2018-07-31 15:09, Matt Sicker wrote:
Is it possible to run nant in a Docker container? I’m not too familiar with
Windows containers.

On Tue, Jul 31, 2018 at 06:55, Dominik Psenner <dpsen...@apache.org> wrote:

I assume that nant was purged from this node with the last
infrastructure update. I can well understand this decision because nant
is an abandoned tool that is heavily outdated. We should have moved away
from it already. Unfortunately this means rewriting all the build
scripts that automate building, testing, generating the assembly version
files, generating the website, .. a total of about 3000 lines of code in
xml format. This is definitely a major task that takes days if not weeks
of development and testing. *sigh*


On 2018-07-30 20:13, Matt Sicker wrote:
Oh no, this is similar to the java 10 errors in log4j2.

On Mon, 30 Jul 2018 at 11:27, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

See <

https://builds.apache.org/job/logging-log4net/job/PR-24/1/display/redirect
------------------------------------------
Branch indexing
Connecting to https://api.github.com using dpsenner/****** (dpsenner at
github)
Loading trusted files from base branch master at
c04a774240fd4500ed3206124aba5b4bc8bc4933 rather than
42ddcc6379c1e007bba5bb9395aa1432a0be5d35
Obtained Jenkinsfile from c04a774240fd4500ed3206124aba5b4bc8bc4933
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
Running on windows-2016-1 in

f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-24-ZGRT4SQ4XLNPR46J4HOG7YQVBJMEQEYWIESHIXY2YXRL6LFYGWWA
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
Cloning the remote Git repository
Cloning with configured refspecs honoured and without tags
Cloning repository https://github.com/apache/logging-log4net.git
   > git init

f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-24-ZGRT4SQ4XLNPR46J4HOG7YQVBJMEQEYWIESHIXY2YXRL6LFYGWWA
# timeout=10
Fetching upstream changes from
https://github.com/apache/logging-log4net.git
   > git --version # timeout=10
using GIT_ASKPASS to set credentials dpsenner at github
   > git fetch --no-tags --progress
https://github.com/apache/logging-log4net.git
+refs/pull/24/head:refs/remotes/origin/PR-24
+refs/heads/master:refs/remotes/origin/master
   > git config remote.origin.url
https://github.com/apache/logging-log4net.git # timeout=10
   > git config --add remote.origin.fetch
+refs/pull/24/head:refs/remotes/origin/PR-24 # timeout=10
   > git config --add remote.origin.fetch
+refs/heads/master:refs/remotes/origin/master # timeout=10
   > git config remote.origin.url
https://github.com/apache/logging-log4net.git # timeout=10
Fetching without tags
Fetching upstream changes from
https://github.com/apache/logging-log4net.git
using GIT_ASKPASS to set credentials dpsenner at github
   > git fetch --no-tags --progress
https://github.com/apache/logging-log4net.git
+refs/pull/24/head:refs/remotes/origin/PR-24
+refs/heads/master:refs/remotes/origin/master
Merging remotes/origin/master commit
c04a774240fd4500ed3206124aba5b4bc8bc4933 into PR head commit
42ddcc6379c1e007bba5bb9395aa1432a0be5d35
   > git config core.sparsecheckout # timeout=10
   > git checkout -f 42ddcc6379c1e007bba5bb9395aa1432a0be5d35
   > git merge c04a774240fd4500ed3206124aba5b4bc8bc4933 # timeout=10
   > git rev-parse "HEAD^{commit}" # timeout=10
Merge succeeded, producing 42ddcc6379c1e007bba5bb9395aa1432a0be5d35
Checking out Revision 42ddcc6379c1e007bba5bb9395aa1432a0be5d35 (PR-24)
   > git config core.sparsecheckout # timeout=10
   > git checkout -f 42ddcc6379c1e007bba5bb9395aa1432a0be5d35
Commit message: "Fixed Spelling."
First time build. Skipping changelog.
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] withEnv
[Pipeline] {
[Pipeline] timeout
Timeout set to expire in 1 hr 0 min
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Tool Install)
[Pipeline] tool
[Pipeline] envVarsForTool
[Pipeline] tool
[Pipeline] envVarsForTool
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Checkout)
[Pipeline] tool
[Pipeline] envVarsForTool
[Pipeline] tool
[Pipeline] envVarsForTool
[Pipeline] withEnv
[Pipeline] {
[Pipeline] checkout
   > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
   > git config remote.origin.url
https://github.com/apache/logging-log4net.git # timeout=10
Fetching without tags
Fetching upstream changes from
https://github.com/apache/logging-log4net.git
   > git --version # timeout=10
using GIT_ASKPASS to set credentials dpsenner at github
   > git fetch --no-tags --progress
https://github.com/apache/logging-log4net.git
+refs/pull/24/head:refs/remotes/origin/PR-24
+refs/heads/master:refs/remotes/origin/master
Merging remotes/origin/master commit
c04a774240fd4500ed3206124aba5b4bc8bc4933 into PR head commit
42ddcc6379c1e007bba5bb9395aa1432a0be5d35
   > git config core.sparsecheckout # timeout=10
   > git checkout -f 42ddcc6379c1e007bba5bb9395aa1432a0be5d35
   > git merge c04a774240fd4500ed3206124aba5b4bc8bc4933 # timeout=10
   > git rev-parse "HEAD^{commit}" # timeout=10
Merge succeeded, producing 42ddcc6379c1e007bba5bb9395aa1432a0be5d35
Checking out Revision 42ddcc6379c1e007bba5bb9395aa1432a0be5d35 (PR-24)
   > git config core.sparsecheckout # timeout=10
   > git checkout -f 42ddcc6379c1e007bba5bb9395aa1432a0be5d35
Commit message: "Fixed Spelling."
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build)
[Pipeline] tool
[Pipeline] envVarsForTool
[Pipeline] tool
[Pipeline] envVarsForTool
[Pipeline] withEnv
[Pipeline] {
[Pipeline] bat

[logging-log4net_PR-24-ZGRT4SQ4XLNPR46J4HOG7YQVBJMEQEYWIESHIXY2YXRL6LFYGWWA]
Running batch script


f:\jenkins\jenkins-slave\workspace\logging-log4net_PR-24-ZGRT4SQ4XLNPR46J4HOG7YQVBJMEQEYWIESHIXY2YXRL6LFYGWWA>F:\jenkins\tools\nant\nant-0.92\bin\NAnt.exe
-buildfile:log4net.build
The system cannot find the path specified.
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Test on Windows)
Stage "Test on Windows" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build-Site)
Stage "Build-Site" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Deploy-Site)
Stage "Deploy-Site" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] step

--
Matt Sicker <boa...@gmail.com>


Reply via email to