gerrit reviews should be able to update any openstack project in launchpad

Bug #1090453 reported by Sean Dague
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure
Confirmed
Medium
Unassigned

Bug Description

We currently have a large number of launchpad project, and even a larger number of git trees that come through gerrit. Some inbound issues aren't always clear which project the final fix is going to come in, especially if we are talking about a devstack, tempest, or docs change.

The current script that posts gerrit reviews into launchpad bugs does a very strict check that that gerrit tree matches the launchpad project, otherwise it won't post. So if a tempest change actually addresses a nova issue, the change won't be posted unless the person was disciplined enough to add tempest as a related project before the push.

In practice that's not happening enough that we are loosing valuable history in our launchpad bugs about related changes happening to address the issue in related projects.

It would be really good if instead of restricting the filter to just the exact launchpad project that matches gerrit, we allow posting to any launchpad that is an openstack project. Then the project could be added as related after gerrit reviews are out there, without any loss of history.

Tags: updatebug
Revision history for this message
Sean Dague (sdague) wrote :
Jeremy Stanley (fungi)
Changed in openstack-ci:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Jeremy Stanley (fungi)
Revision history for this message
Thierry Carrez (ttx) wrote :

The idea would be to comment on the bug in all cases, but update the bugtask status only if a project matches.
Fungi: I know that codebase well, I can take it if you prefer.

tags: added: updatebug
Revision history for this message
Jeremy Stanley (fungi) wrote :

I didn't mean to wind up squatting this ticket. Unfortunately after a couple of false starts refactoring the script to start using our projects.yaml tooling, this sat unaddressed far longer than I would like. If you decide you want to tackle it soon, I'll just rebase my work on top of it later.

Changed in openstack-ci:
assignee: Jeremy Stanley (fungi) → Thierry Carrez (ttx)
Revision history for this message
Thierry Carrez (ttx) wrote :

It's less trivial than I thought, since update-bug logic is to find bugtasks and then act on them (rather than act and then maybe find corresponsing bugtasks). It needs to be done the other way around to support this, and I don't have time to spend on this right now... so unassigning myself to give someone else a chance to do it.

Changed in openstack-ci:
assignee: Thierry Carrez (ttx) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.