graph of number of packages built from branches
Bug #674353 reported by
Martin Pool
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Distributed Development |
Confirmed
|
High
|
canonical-bazaar |
Bug Description
We'd like a metric/graph of the number of packages (in main, in ppas, etc) that have been built using UDD. There was some discussion of this on the udd list, suggesting we could insert a metadata field into the packages when they are built, and then scan this out from soyuz or similar.
The dependency chain for this is somewhat long because it seems to require changing both bzr-builddeb and soyuz; the latter may be hard.
At the moment we have graphs of the number of people using package branches, the number of package branches, and the number of recipes.
Changed in udd: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in udd: | |
assignee: | nobody → canonical-bazaar (canonical-bazaar) |
To post a comment you must log in.
On Fri, 2010-11-12 at 03:46 +0000, Martin Pool wrote:
> We'd like a metric/graph of the number of packages (in main, in ppas,
> etc) that have been built using UDD. There was some discussion of this
> on the udd list, suggesting we could insert a metadata field into the
> packages when they are built, and then scan this out from soyuz or
> similar.
>
> The dependency chain for this is somewhat long because it seems to
> require changing both bzr-builddeb and soyuz; the latter may be hard.
Perhaps this can be done by using a control field in the changes file.
This should be possible by having bzr-builder insert a XC-Foo header in
the source package control file, using python-debian.
Soyuz already has the infrastructure to pick up new custom control /code.launchpad .net/~jelmer/ launchpad/ 621778- homepage- field/+ merge/33331 and https:/ /code.launchpad .net/~jelmer/ launchpad/ 621778- parse-homepage- field/+ merge/33334
fields. At the moment they end up in a JSON'ed dictionary, so that's not
easily searchable using SQL. It shouldn't be too hard to add another
database field to the table though. I recently did a similar thing for
the Homepage field:
https:/
It would be nice if a field is being added anyway, to use it to identify
the specific manifest that was build. This would allow us to link back
to individual Bazaar revisions that were used to build for each UDD
package that was uploaded.
Cheers,
Jelmer