I must mention that the Dockerfiles are invoked from the Jenkinsfile and uses nant and the nant build scripts to build the project. nant is a deadend road and should be replaced. The dockerfiles could stay, providing the future build requisites for the future build scripts. If the project is migrated to the new SDK style, it would be supported by the dotnet commandline tool and as such the following targets can be built by using the dotnet build command:
https://docs.microsoft.com/en-us/dotnet/standard/frameworks https://docs.microsoft.com/it-it/dotnet/core/tools/dotnet-build This would greatly integrate with msbuild inline tasks which could be used to build site and other non-code assemblies: https://docs.microsoft.com/en-us/visualstudio/msbuild/msbuild-inline-tasks?view=vs-2019 Cheers, Dominik On Sun, 19 Apr 2020 at 10:41, Dominik Psenner <[email protected]> wrote: > You may find the develop and other branches useful: > > https://github.com/apache/logging-log4net/tree/develop/buildtools/docker > <https://github.com/apache/logging-log4net/tree/feature/netstandard-2.0/buildtools/docker> > > There are dockerfiles along with shell scripts that used to work for > building several of the targets. > -- > Sent from my phone. Typos are a kind gift to anyone who happens to find > them. > > On Sat, Apr 18, 2020, 17:02 Davyd McColl <[email protected]> wrote: > >> A short update (not much to report): >> >> - resolved Client profile builds >> - can manually build a .nupkg, without any warnings >> - have updated <licenseUrl> to <license>, using the term Apache-2.0, as >> per the url it was pointing to >> - have updated <iconUrl> to point at the same feather.png the package >> used to point to online, renamed within the project to package-icon.png for >> clarity >> >> Next up: >> dotnet core tooling wants sdks for net20 and net35 to be installed on the >> host. Alternatively, we could install all of Build Tools 2019 on the host. >> I think the former might be neater. At any rate, I now have to figure out >> enough docker to be dangerous and get a standalone build environment up and >> running. >> >> -d > > -- Dominik Psenner
