API call for finding branches that contain a revid

Bug #356360 reported by Jelmer Vernooij
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

It would be useful if there was some way to find *any* branch on launchpad that contained a particular revision id. This would be useful for example when writing a plugin that short-circuits revision imports from foreign branches.

e.g. if I was doing a "bzr clone of git://git.kernel.org/pub/linux-2.6.git" the plugin could recognize that some bzr revids it would generate were already present in e.g. lp:~vcs-imports/linux/2.6 and fetch them from there instead (as that would be significantly faster than importing from git).

Tags: api lp-code
Revision history for this message
Jonathan Lange (jml) wrote :

Seems sensible enough.

Changed in launchpad-bazaar:
importance: Undecided → Low
status: New → Triaged
summary: - API call for finding branch that contains a revid
+ API call for finding branches that contain a revid
tags: added: api
Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

This sounds like the best option for the Q/A scripting machinery to tie commits to bugs right now. I understand that the branch revision table is enormous though... is there any risk of performance limitations scuppering this option?

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Once this is implemented, we can track Q/A through bugs: you land a branch to fix bug X, and bug X automatically gets tagged as needing Q/A. The tags make it easy to view Q/A workload for persons, teams, categories, etc.

In the Translations team we've been working this way for a few months and it works very nicely—except this bug is the missing link for the scripts to figure out the right bug based on a commit.

Revision history for this message
Aaron Bentley (abentley) wrote : Re: [Bug 356360] Re: API call for finding branches that contain a revid

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeroen T. Vermeulen wrote:
> Once this is implemented, we can track Q/A through bugs: you land a
> branch to fix bug X, and bug X automatically gets tagged as needing Q/A.
> The tags make it easy to view Q/A workload for persons, teams,
> categories, etc.
>
> In the Translations team we've been working this way for a few months
> and it works very nicely—except this bug is the missing link for the
> scripts to figure out the right bug based on a commit.

We already automatically link branches to bugs based on a commit. Why
do you need something else?

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAktoUfkACgkQ0F+nu1YWqI1duwCfQVWdzUJQAu8/cjcbRPrdC2+I
oVkAn2vADeBZu1OT3rMJxB+i2xDQ2cfO
=5UiM
-----END PGP SIGNATURE-----

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

The script needs to find the right branch, given a revision. The connection all the way to the bug is currently made through textual tags in merge messages.

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.