Hi all
I've raised a PR (https://github.com/apache/logging-log4net/pull/59). I'm sure
there's more to be done, process-wise. I'd really appreciate some guidance.
-d
On 2020-05-03 19:32:14, Ralph Goers wrote:
There is nothing that requires the release build to run on ASF hardware if that
There is nothing that requires the release build to run on ASF hardware if that
helps. I perform all the Log4j releases on my MacBook Pro.
That said, I am sure it would be helpful to have Docker available to preform CI
builds.
Ralph
> On May 3, 2020, at 10:23 AM, Davyd McColl wrote:
>
> Hi
I'm not sure if our Jenkins here is set up for Docker on Windows yet
as that's even a fairly recent integration being worked on in Jenkins
itself right now (mostly around packaging Jenkins in a Windows Docker
container, but it's part of the larger experience). If you already
have it working on
Hi Ralph
I'll add documentation about build, though it's either:
1. run the batch file to run the docker image and build through that
or
2. let AppVeyer build by itself -- which it does -- and grab the build artifact
from that, which I don't currently do, as I'm not sure where to put it or how
All releases at the ASF follow the guidelines at
https://infra.apache.org/release-publishing.html. Although each project is free
the tailor the release process to meed its needs, the end result must comply
with what is documented there. For example, Log4j 2 uses
Hi all
I've been a bit busy with other stuff lately, but played a little catch-up
today:
- I have a _windows_ docker image (and batch file) which builds log4net fine
- I've sorted out AppVeyer -- builds happen fine there too. I get the nuget
package as a build artifact -- I'd guess that, at
Sounds great so far! You can also look at GitHub Actions to see if there’s
anything useful there for CI. That’s relatively new, but there might
already be some good .net actions to use.
On Mon, Apr 13, 2020 at 09:13 Davyd McColl wrote:
> Hi all
>
> Since there was interest in intermittent
Hi all
Since there was interest in intermittent status updates, here's a short one:
1. Packaged & released my build scripts as an npm module (zarro)
2. Consolidated the netstandard and main log4net projects and re-organised the
code locations to be more consistent with .net style: src folder
