Hi
I've just disabled both old build jobs in jenkins before they get on our
nerves. :-) Further I've updated the following files both to be in markup
and parts of their contents to reflect more the current state of the
project:
* README
* CONTRIBUTING
* ReleaseInstructions
Please note that Relea
I have created this INFRA ticket regarding .net-2.0, node labels and the
missing .net-3.5 on windows-2012-3:
https://issues.apache.org/jira/browse/INFRA-14645
2017-07-19 10:54 GMT+02:00 Dominik Psenner :
>
>
> On 19 Jul 2017 6:35 a.m., "Stefan Bodewig" wrote:
>
> On 2017-07-18, Dominik Psenner
On 19 Jul 2017 6:35 a.m., "Stefan Bodewig" wrote:
On 2017-07-18, Dominik Psenner wrote:
> oohh how I like to be the bringer of good news! Right now I was finally
> able to fix the building of the netstandard target by providing a
> jenkinsfile script that detects the UID and GID of the working p
On 2017-07-18, Dominik Psenner wrote:
> oohh how I like to be the bringer of good news! Right now I was finally
> able to fix the building of the netstandard target by providing a
> jenkinsfile script that detects the UID and GID of the working path and
> passing that in as parameters into the bui
Hi,
oohh how I like to be the bringer of good news! Right now I was finally
able to fix the building of the netstandard target by providing a
jenkinsfile script that detects the UID and GID of the working path and
passing that in as parameters into the builder-netstandard dockerfile when
it is bui
If this was not about hacking it would be a lot easier to accomplish. 😁
I found also out that it is good practice to add arguments to the
dockerfile. This would then be the interface to pass in environment
variables of jenkins. A good candidate could be WORKSPACE and extract uid
and gid inforation
Alternatives that may allow us to do the same are gosu and su-exec. Note
that sudo won't work.
On 10 Jul 2017 10:25 a.m., "Dominik Psenner" wrote:
> I just stumbled upon this which may allows us to detect the expected uid
> that a docker container is run in when the docker container is built. We
On 2017-07-10, Dominik Psenner wrote:
> I just stumbled upon this which may allows us to detect the expected uid
> that a docker container is run in when the docker container is built. We
> can use that information to prepare the docker container user so that its
> uid and gid match the one we nee
I just stumbled upon this which may allows us to detect the expected uid
that a docker container is run in when the docker container is built. We
can use that information to prepare the docker container user so that its
uid and gid match the one we need later when the docker container is run:
http
>
> dotnet test inside of the directory is what I've done so far.
>>
>> Stefan
>>
>
> I'm adding dotnet test into the jenkinsfile. We'll see what happens. :-)
>
This is the outcome. So something works, but I see no tests and a strange
warning.
{quote}
[log4net_feature_cd-pipeline-76KUCPODUF6LCE4
2017-07-09 18:22 GMT+02:00 Stefan Bodewig :
> On 2017-07-09, Dominik Psenner wrote:
>
> > I finally managed to build the netstandard assemblies in our jenkins
> > pipeline. It was a tough task and the solution feels like a hack, but it
> > works. See:
>
> > https://builds.apache.org/job/logging-lo
On 2017-07-09, Dominik Psenner wrote:
> I finally managed to build the netstandard assemblies in our jenkins
> pipeline. It was a tough task and the solution feels like a hack, but it
> works. See:
> https://builds.apache.org/job/logging-log4net/job/develop/
> The problem was that dotnet always
Ok, the hack has its price. The uid is not always the same and therefore
builds may randomly fail:
https://builds.apache.org/job/logging-log4net/view/change-requests/job/PR-8/9/console
This is a call for help. Does anyone have a good idea how this issue can be
solved for good?
2017-07-09 17:37 G
Hi,
I finally managed to build the netstandard assemblies in our jenkins
pipeline. It was a tough task and the solution feels like a hack, but it
works. See:
https://builds.apache.org/job/logging-log4net/job/develop/
The problem was that dotnet always attempts to find and store dependent
assembl
14 matches
Mail list logo
