[JIRA] (JENKINS-48430) Provided config file is sometimes not complete

[domi@fortysix.ch (JIRA)]

Dominik Bartholdi commented on JENKINS-48430

Re: Provided config file is sometimes not complete I tried to reproduce this issue, but even with the provided pipeline and more then 100 executions, I was not able to do so   Most likely, the problem is somewhere in org.jenkinsci.lib.configprovider.model.ConfigFileManager#provisionConfigFile , but so far I did not find the culprit... Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[aviad10m@gmail.com (JIRA)]

Aviad M commented on JENKINS-48430

Re: Provided config file is sometimes not complete

For some reason my thread has been closed. We suffer from this a lot.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[aviad10m@gmail.com (JIRA)]

Aviad M edited a comment on JENKINS-48430

Re: Provided config file is sometimes not complete

For some reason my thread has been closed. We suffer from this a lot.

Plugin version: 2.18 Jenkins version: 2.89

Add Comment

[domi@fortysix.ch (JIRA)]

Dominik Bartholdi commented on JENKINS-48430

Re: Provided config file is sometimes not complete

Aviad M can you provide some more background? so far I was not able to reproduce this issue, even with 10'000 executions of a job.   e.g. how does your environment look like? master only? or slaves? what OS? size of files? config file type? ...

Add Comment

[aviad10m@gmail.com (JIRA)]

Aviad M commented on JENKINS-48430

Re: Provided config file is sometimes not complete

Dominik Bartholdi It's a master and 5-6 slaves. Linux (Ubuntu 16.04 servers) and windows (2012 servers) slaves, however the problem occurs on the linux slaves (haven't tried personally the windows ones). I save a plain config file in a .env  format.   It takes some build attempts in order to the file successfully being present in the slave machine. I have, like the author of this thread, an IF clause alerting me if the file not present when the build starts. More details here.

Add Comment

[aviad10m@gmail.com (JIRA)]

Aviad M edited a comment on JENKINS-48430

Re: Provided config file is sometimes not complete

[~imod]

It's a master and 5-6 slaves. Linux (Ubuntu 16.04 servers) and windows (2012 servers) slaves, however the problem occurs on the linux slaves (haven't tried personally the windows ones).

I save a plain config file in a [.env|https://www.npmjs.com/package/dotenv] format.

It takes some build attempts in order to the file successfully being present in the slave machine. I have, like the author of this thread, an IF clause alerting me if the file not present when the build starts.

More details  [ here |https://issues . jenkins-ci.org/browse/JENKINS-51750].

Add Comment

[aviad10m@gmail.com (JIRA)]

Aviad M edited a comment on JENKINS-48430

Re: Provided config file is sometimes not complete

[~imod] It's a master and 5-6 slaves. Linux (Ubuntu 16.04 servers) and windows (2012 servers) slaves, however the problem occurs on the linux slaves (haven't tried personally the windows ones).

I save a plain config file in a [.env |https://www. google npmjs . co.il com / search?q=npm+ package/ dotenv &oq=npm+dotenv&aqs=chrome..69i57j0l5.1933j0j7&sourceid=chrome&ie=UTF-8 ] format.

It takes some build attempts in order to the file successfully being present in the slave machine. I have, like the author of this thread, an IF clause alerting me if the file not present when the build starts. More details

[ here |https://issues . jenkins-ci.org/browse/JENKINS-51750].

Add Comment

[domi@fortysix.ch (JIRA)]

Dominik Bartholdi commented on JENKINS-48430

Re: Provided config file is sometimes not complete

I would very much like to fix this, but as stated previously, I'm not able to reproduce the issue in my env. I have an idea for a fix, but would need someone to try it before I ship it. Anyone willing to help/test out?

Add Comment