-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Jenkins 1.609.3
release-plugin:2.5.4
credentials-binding-plugin:1.9
Problem
Injecting credentials through the credentials-binding plugin is done too late when using the prebuild steps of the release-plugin.
The credentials-binding plugin is executed after the prebuild steps of the release-plugin, so any injected credentials cannot be used it.
Steps to reproduce
- Inject a secret through the credentials-binding plugin
- Enable 'configure a release' build wrapper
- Configure the release-plugin with a pre-release shell step, which echoes the injected secret to build log
- Create a normal shell build step which echoes the injected secret to build log
See trigger-release-build.txt for an output of the above steps.
You see that the injected secret is not available in the pre-release step of the release-plugin buildwrapper, but it is in the normal build step.
Expected behavior
As a user, I can inject the credentials and use them with the pre-release steps of the release-plugin.
- mentioned in
-
Page Loading...