-
Bug
-
Resolution: Fixed
-
Major
Currently when you use withCredentials with e.g. UsernamePasswordMultiBinding, the secret is saved in program.dat for the duration of the block. It is later removed, but it would be safer if it were guaranteed to never be persisted at all. That seems to require an API change: either in EnvVars to allow a given variable to be directly marked as secret and thus to be persisted only via Secret, or by lifting up sensitiveBuildVariables from AbstractBuild to Run, or by allowing BodyInvoker.withContext to provide something like an environment variable factory rather than a raw EnvVars.
- is related to
-
JENKINS-26128 Dynamically-scoped env step
- Resolved
-
JENKINS-28719 Store environment variable values for CoreWrapperStep as Secret
- Open
- links to