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 this pull request into a Git repository by running:
$ git pull https://github.com/apache/logging-log4net
feature/build-multibranch
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/logging-log4net/pull/12.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #12
----
commit cb03eeede4d231f2bd89bbf71941df3f90836b84
Author: Dominik Psenner <[email protected]>
Date: 2017-06-30T08:58:58Z
Added a first jenkinsfile that does echo on a windows node.
commit 619e0d013a65832a1c54ccb1f94c7f5c8cc5844e
Author: Dominik Psenner <[email protected]>
Date: 2017-06-30T09:43:55Z
Changed node to windows-2012-2
commit 6446ed929f3512db9e8ffb040a435e8622c953a5
Author: Dominik Psenner <[email protected]>
Date: 2017-06-30T09:53:41Z
Changed label to Windows
commit 3476d605c5912256eb93cf02a0e9127868bc6dfc
Author: Dominik Psenner <[email protected]>
Date: 2017-06-30T10:04:36Z
Added dir to get a view of the directory structure
commit ef58a9acaab92f8bf3279c43c27026adb55b4515
Author: Dominik Psenner <[email protected]>
Date: 2017-06-30T10:18:59Z
Fixed cmd to read as bat
commit e6cc8700f79fdca318d3d078f43dc2d32ae4b22e
Author: Dominik Psenner <[email protected]>
Date: 2017-06-30T10:23:32Z
Invoke build.cmd and see what happens
commit e62f95888a410a869492d21fd443b639f142a105
Author: Dominik Psenner <[email protected]>
Date: 2017-06-30T11:02:22Z
echo ANT_HOME
commit 027f2ad130c8840bc2b3e68ac6876ae59691dc5c
Author: Dominik Psenner <[email protected]>
Date: 2017-06-30T11:10:54Z
Set ant environment variable and add ant to path
commit 5ab062c8964469286f84b3cf038248b1f6f3f4ad
Author: Dominik Psenner <[email protected]>
Date: 2017-06-30T12:38:53Z
Trying to figure out the nant tool installation path
commit cafc88dfe0c71bd367f0ccc1af48243c3f12ec22
Author: Dominik Psenner <[email protected]>
Date: 2017-06-30T12:52:33Z
Hard-wired nant installation for now
commit cc40c85896179317624e2d123768319b9323d42f
Author: Dominik Psenner <[email protected]>
Date: 2017-06-30T12:58:52Z
Try to invoke build.cmd now that nant.exe is in the path
commit c4afbb53313c8653f0086a277ca1ad0fb6e22bf8
Author: Dominik Psenner <[email protected]>
Date: 2017-06-30T13:15:47Z
Added stage test and added direct invocation of nant
----
---
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 feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
