Jenkins jobs are always running for abandoned patches
Bug #1316064 reported by
wingwj
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Core Infrastructure |
Fix Released
|
High
|
James E. Blair |
Bug Description
Jenkins met some problems about abandoned patches.
The Jenkins-jobs are always running even if the jobs were successful or failed..
I've checked some patches[1][2][3] suit the issue.
It look like if you add comments to an abandoned patch, the Jenkins will start check jobs again and again..
[1] https:/
[2] https:/
[3] https:/
Changed in openstack-ci: | |
assignee: | nobody → wingwj (wingwj) |
Changed in openstack-ci: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | wingwj (wingwj) → James E. Blair (corvus) |
milestone: | none → icehouse |
To post a comment you must log in.
Another example: https:/ /review. openstack. org/#/c/ 82627/
That change got abandoned with Jenkins V+1 and a CR-1. Joshua commented on it and that triggered a loop of 'check' jobs.