-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Jenkins 2.21 on Linux x86-64
Promoted Builds Plugin 2.27
I want to establish a QA pipe like described in the documentation of the plugin.
Therefor, I have the following promotion steps:
DeployStaging
- only when manually approved
TestedOnStaging
- only when manually approved
- when upstream promotions promoted: DeployStaging
DeployProduction
- only when manually approved
- when upstream promotions promoted: TestedOnStaging
So my intention is that first some has to trigger the deployment on the staging server, then it has to be tested and only if that was approved, it can be deployed to the production server.
Now when no step was every promoted and I trigger DeployProduction, it correctly tells me "Unmet qualification: TestedOnStaging".
Then I trigger TestedOnStaging and it correctly tells me that DeployStaging qualification was not met.
But if I now trigger DeployStaging, it deploys, automatically triggers TestedOnStaging and then automatically triggers DeployProduction.
Is this behavior intended? As I cannot undo a manually promotion, I think that the behavior is very risky and may force unintended behavior.
[JENKINS-38170] Manual approval is stored, even if requirements are not matched
Max Wahler
created issue -
| Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |