[JIRA] (JENKINS-38170) Manual approval is stored, even if requirements are not matched
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Sorry, over last months I had no time to work on the plugin, because I had to focus on the Jenkins core and other projects. I also have not been using this plugin on my own since 2016. So I have decided to unassign the issues so that there is no expectation that I work on them anytime soon. Currently the plugin is being transfered to another maintainer. Hopefully he will have some time to finish triaging of the issues and maybe to deliver some fixes. But, as in any community-driven project, everybody is welcome to propose pull requests and to contribute to the plugin's state. Jenkins / JENKINS-38170 Manual approval is stored, even if requirements are not matched Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-38170) Manual approval is stored, even if requirements are not matched
Title: Message Title Max Wahler created an issue Jenkins / JENKINS-38170 Manual approval is stored, even if requirements are not matched Issue Type: Bug Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 2016/Sep/13 3:00 PM Environment: Jenkins 2.21 on Linux x86-64 Promoted Builds Plugin 2.27 Priority: Critical Reporter: Max Wahler 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 n
