CloudBees Jenkins Platform 188.8.131.52
RELEASED: Public: 2019-07-03
Based on Jenkins
Pipeline stages, parallels, and step incorrectly marked unstable
When there is a build with an unstable stage, parallel, or step, all the stages, parallels, and steps are incorrectly marked as unstable instead of just the unstable one that caused the Pipeline to be unstable. This is a known issue in the
System.exit(int) and similar methods could still be approved in Script Approval, but there’s never a good reason for them to be usable in Pipeline scripts. These methods are now blocked permanently from all sandboxed Groovy execution in Jenkins.
Uses of the Git plugin’s mergeStrategy option in Pipeline started failing in Git 3.9.0 if the specified value was not uppercase. The value of the mergeStrategy option may now be specified in any case in a Pipeline.
The git plugin fetched to the local cache before checking remote references for updates causing MissingObjectException if references got updated between these operations. The problem is more notable on large repositories where the fetch operation can take a long time. The fix changes the order of the operations making the issue less likely to occur since listing references is fairly quick.
Certain sandboxed Groovy script idioms, including but not limited to Pipeline, could result in a build failure with a RejectedAccessException without Jenkins offering the corresponding signature as a pending approval. Script Security rejections will now be reported properly in all contexts.
When users of the EC2, docker-commons, and SSH credentials plugins updated passwords, the original passwords were not hidden nor were previous values encrypted. With this fix, when users of the EC2, docker-commons, and SSH credentials plugins update passwords, the original passwords are hidden and previous values encrypted.