Jenkins jobs are always running for abandoned patches

Bug #1316064 reported by wingwj on 2014-05-05
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure
Fix Released
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..


wingwj (wingwj) on 2014-05-05
Changed in openstack-ci:
assignee: nobody → wingwj (wingwj)
Antoine "hashar" Musso (hashar) wrote :

Another example:

That change got abandoned with Jenkins V+1 and a CR-1. Joshua commented on it and that triggered a loop of 'check' jobs.

Jeremy Stanley (fungi) wrote :

The fix for this is already pending at but until it's approved and zuul restarted, you can work around the behavior by restoring (un-abandoning) the change long enough for zuul to successfully land a vote on it, then abandoning it again.

Jeremy Stanley (fungi) on 2014-05-05
Changed in openstack-ci:
status: New → In Progress
importance: Undecided → High
assignee: wingwj (wingwj) → James E. Blair (corvus)
milestone: none → icehouse
Jeremy Stanley (fungi) wrote : merged 05-05 23:31 UTC.

Changed in openstack-ci:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers