-
Improvement
-
Resolution: Fixed
-
Minor
-
None
See JENKINS-44621 and friends for something similar. The properties step will nuke every JobProperty on the job (other than BranchJobProperty), even if that JobProperty was defined outside of the Jenkinsfile, such as for non-multibranch jobs in the UI. We can set things up to be smarter about that and ignore any JobProperty not defined in the previous Jenkinsfile.
- is duplicated by
-
JENKINS-45053 EnvInject Properties are lost when 'properties' is used in a pipeline step
- Resolved
- relates to
-
JENKINS-41875 Cannot remove properties from Jenkinsfile for Pipeline from SCM
- Resolved
- links to