• Type: Bug
• Resolution: Fixed
• Priority: Critical
• Component/s: gradle-plugin
• Labels:

  • regression
• Environment:

  Windows 10, Jenkins 2.392, gradle-plugin 2.3

[JENKINS-70692] Setting a node temporarily offline removes ENV settings

Jens Beyer created issue - 2023-02-27 08:32

Jens Beyer made changes - 2023-02-27 10:30

Description

Original: We have a Jenkins node configured with an environment variable. Everytime we set this node offline temporarily (using the markOffline function in Jenkins UI), and then restart the machines (I'm not sure if it's the slave or the server), after the restart, the environment variable is still there, but the value is empty. Configuration History plugin shows that there is an Entry with source SYSTEM, which contains two Changes - the marking as offline (<temporaryOfflineCause class="hudson.slaves.OfflineCause$UserCause">), and the removal of this ENV value. If I don't restart while the node is set to offline, there is no issue. Please let me know what else information you need, it's probably a complex to follow issue. The false behavior started after the last update of jenkins core and our plugins. It's been correct before. It's less than two weeks old.

New: We have a Jenkins node configured with an environment variable. Everytime we set this node offline temporarily (using the markOffline function in Jenkins UI), and then restart the machines, after the restart, the environment variable is still there, but the value is empty. I'm not sure if it's the slave or the server reboot which is causing the issue, I can try to find out if it helps. Configuration History plugin shows that there is an Entry with source SYSTEM, which contains two Changes - the marking as offline (<temporaryOfflineCause class="hudson.slaves.OfflineCause$UserCause">), and the removal of this ENV value. If I don't restart while the node is set to offline, there is no issue. Please let me know what else information you need, it's probably a complex to follow issue. The false behavior started after the last update of jenkins core and our plugins. It's been correct before. It's less than two weeks old.

Collapse comment: Jens Beyer added a comment - 2023-02-27 11:51, Edited by Jens Beyer - 2023-03-01 07:53

Jens Beyer added a comment - 2023-02-27 11:51 - edited

Could be related to JENKINS-69922

Very likely related to JENKINS-70663

Expand comment: Jens Beyer added a comment - 2023-02-27 11:51, Edited by Jens Beyer - 2023-03-01 07:53

Jens Beyer added a comment - 2023-02-27 11:51 - edited Could be related to JENKINS-69922 Very likely related to JENKINS-70663

Jens Beyer made changes - 2023-02-27 12:36

Description

Original: We have a Jenkins node configured with an environment variable. Everytime we set this node offline temporarily (using the markOffline function in Jenkins UI), and then restart the machines, after the restart, the environment variable is still there, but the value is empty. I'm not sure if it's the slave or the server reboot which is causing the issue, I can try to find out if it helps. Configuration History plugin shows that there is an Entry with source SYSTEM, which contains two Changes - the marking as offline (<temporaryOfflineCause class="hudson.slaves.OfflineCause$UserCause">), and the removal of this ENV value. If I don't restart while the node is set to offline, there is no issue. Please let me know what else information you need, it's probably a complex to follow issue. The false behavior started after the last update of jenkins core and our plugins. It's been correct before. It's less than two weeks old.

New: We have a Jenkins node configured with an environment variable. Everytime we set this node offline temporarily (using the markOffline function in Jenkins UI), and then restart the machines, after the restart, the environment variable is still there, but the value is empty. I'm not sure if it's the slave or the server reboot which is causing the issue, I can try to find out if it helps. Configuration History plugin shows that there is an Entry with source SYSTEM, which contains two Changes - the marking as offline (<temporaryOfflineCause class="hudson.slaves.OfflineCause$UserCause">), and the removal of this ENV value. If I don't restart while the node is set to offline, there is no issue. If I set it back online, then restart, there is no issue either. Please let me know what else information you need, it's probably a complex to follow issue. The false behavior started after the last update of jenkins core and our plugins. It's been correct before. It's less than two weeks old.

Jens Beyer made changes - 2023-02-27 12:41

Summary

Original: Setting a node offline temporarily removes ENV settings

New: Setting a node temporarily offline removes ENV settings

Jens Beyer made changes - 2023-03-01 07:53

Description

Original: We have a Jenkins node configured with an environment variable. Everytime we set this node offline temporarily (using the markOffline function in Jenkins UI), and then restart the machines, after the restart, the environment variable is still there, but the value is empty. I'm not sure if it's the slave or the server reboot which is causing the issue, I can try to find out if it helps. Configuration History plugin shows that there is an Entry with source SYSTEM, which contains two Changes - the marking as offline (<temporaryOfflineCause class="hudson.slaves.OfflineCause$UserCause">), and the removal of this ENV value. If I don't restart while the node is set to offline, there is no issue. If I set it back online, then restart, there is no issue either. Please let me know what else information you need, it's probably a complex to follow issue. The false behavior started after the last update of jenkins core and our plugins. It's been correct before. It's less than two weeks old.

New: We have a Jenkins node configured with an environment variable (MAVEN_OPTS). Everytime we set this node offline temporarily (using the markOffline function in Jenkins UI), and then restart the machines, after the restart, the environment variable is still there, but the value is empty. I'm not sure if it's the slave or the server reboot which is causing the issue, I can try to find out if it helps. Configuration History plugin shows that there is an Entry with source SYSTEM, which contains two Changes - the marking as offline (<temporaryOfflineCause class="hudson.slaves.OfflineCause$UserCause">), and the removal of this ENV value. If I don't restart while the node is set to offline, there is no issue. If I set it back online, then restart, there is no issue either. Please let me know what else information you need, it's probably a complex to follow issue. The false behavior started after the last update of jenkins core and our plugins. It's been correct before. It's less than two weeks old.

Collapse comment: Basil Crow added a comment - 2023-03-09 23:28

Basil Crow added a comment - 2023-03-09 23:28

The false behavior started after the last update of jenkins core and our plugins. It's been correct before. It's less than two weeks old.

What are the steps to reproduce the problem from scratch? What is the last weekly release in which the scenario passes, and what is the first weekly release in which the scenario fails?

Expand comment: Basil Crow added a comment - 2023-03-09 23:28

Basil Crow added a comment - 2023-03-09 23:28 The false behavior started after the last update of jenkins core and our plugins. It's been correct before. It's less than two weeks old. What are the steps to reproduce the problem from scratch? What is the last weekly release in which the scenario passes, and what is the first weekly release in which the scenario fails?

Basil Crow made changes - 2023-03-09 23:28

Labels

New: regression

Jens Beyer made changes - 2023-03-10 05:37

Component/s		New: gradle-plugin [ 15547 ]
Component/s	Original: core [ 15593 ]

Jens Beyer made changes - 2023-03-10 05:37

Environment

Original: Windows 10, Jenkins 2.392

New: Windows 10, Jenkins 2.392, gradle-plugin 2.3

Load more newer events