[JIRA] (JENKINS-59926) EnvInject of properties file fails on some slaves

5 views
Skip to first unread message

moshe.zvi@gmail.com (JIRA)

unread,
Oct 24, 2019, 5:18:03 PM10/24/19
to jenkinsc...@googlegroups.com
Moshe Zvi created an issue
 
Jenkins / Bug JENKINS-59926
EnvInject of properties file fails on some slaves
Issue Type: Bug Bug
Assignee: Unassigned
Attachments: envinject.zip
Components: envinject-plugin
Created: 2019-10-24 21:17
Environment: Jenkins 2.190.1 (also in 2.176.1)
EnvInject plugin 2.3.0 (also in 2.2.1)
Priority: Critical Critical
Reporter: Moshe Zvi

This relates to JENKINS-59892, but I've managed to narrow it down.
The same job was run on two identical slaves. the job writes a property to a file, injects the file, and then attempts to echo it.
On one slave this succeeds, on another it fails. This is killing our system - many jobs fail due to missing attributes.
I've attached all the configuration files i could think of in the zip.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

moshe.zvi@gmail.com (JIRA)

unread,
Oct 24, 2019, 5:19:02 PM10/24/19
to jenkinsc...@googlegroups.com
Moshe Zvi updated an issue
Change By: Moshe Zvi
This relates to JENKINS-59892, but I've managed to narrow it down.
The same job was run on two identical slaves. the job writes a property to a file, injects the file, and then attempts to echo it.
On one slave this succeeds, on another it fails. This is killing our system - many jobs fail due to missing attributes.
I've attached all the configuration files i could think of in the zip.

Note:
As a comparison, I also tried injecting a variable not from a file - that succeeds in both (see VAR_IN_FILE vs. VAR_IN_CONTENT in the injectedEnvVars files).

moshe.zvi@gmail.com (JIRA)

unread,
Oct 24, 2019, 5:25:02 PM10/24/19
to jenkinsc...@googlegroups.com
Moshe Zvi updated an issue
This relates to JENKINS-59892, but I've managed to narrow it down.
The same job was run on two identical slaves. the job writes a property to a file, injects the file, and then attempts to echo it.
On one slave this succeeds, on another it fails. This is killing our system - many jobs fail due to missing attributes.
I've attached all the configuration files i could think of in the zip.

Note:
As a comparison, I also tried injecting a variable not from a file - that succeeds in both (see VAR_IN_FILE vs. VAR_IN_CONTENT in the injectedEnvVars files).

Additional info:
I tried using a full path (as opposed to a partial path) and it seems to work (e.g. $WORKSPACE/build.properties vs. build.properties).
Reply all
Reply to author
Forward
0 new messages