-
Bug
-
Resolution: Fixed
-
Critical
https://github.com/jenkinsci/jenkins/blob/7376aa0e292c5df6ec7dd46bf0e399d93911348e/core/src/main/java/jenkins/security/s2m/MasterKillSwitchConfiguration.java#L50 does not consider the case where you do not have any fixed slaves but you have at least one cloud that can provide slaves.
- is related to
-
JENKINS-31596 The MasterKillSwitchConfiguration should always be relevant if security is enabled
-
- Closed
-
[JENKINS-31591] MasterKillSwitchConfiguration is not available when you have clouds but no fixed slaves
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Link |
New:
This issue is related to |
Link | New: This issue is blocking SECURITY-144 [ SECURITY-144 ] |
Labels | Original: lts-candidate | New: cloud lts-candidate security |
Labels | Original: cloud lts-candidate security | New: 1.625.3-rejected cloud security |
Labels | Original: 1.625.3-rejected cloud security | New: 1.625.3-rejected cloud lts-candidate security |
Code changed in jenkins
User: Stephen Connolly
Path:
core/src/main/java/jenkins/security/s2m/MasterKillSwitchConfiguration.java
http://jenkins-ci.org/commit/jenkins/e8f2002c466c49eff4a7be0cc4633580515cd7a5
Log:
[FIXED JENKINS-31591] Correct MasterKillSwitchConfiguration visibility