graph of number of packages built from branches

Bug #674353 reported by Martin Pool on 2010-11-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Distributed Development
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.

Tags: udd Edit Tag help
Martin Pool (mbp) on 2010-11-12
Changed in udd:
status: New → Confirmed
importance: Undecided → High

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
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://code.launchpad.net/~jelmer/launchpad/621778-homepage-field/+merge/33331 and https://code.launchpad.net/~jelmer/launchpad/621778-parse-homepage-field/+merge/33334

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

Martin Pool (mbp) wrote :

https://bugs.launchpad.net/udd/+bug/676766 is about the specific implementation option of putting a marker in the package header.

Martin Pool (mbp) on 2011-01-10
Changed in udd:
assignee: nobody → canonical-bazaar (canonical-bazaar)
Martin Pool (mbp) wrote :

After some discussion last week: we still want graphs, but the specific thing of tracking them by inserting headers seems like a waste of effort, if the only point is to produce a graph. Instead, we'll use this bug to request tracking by just monitoring something we already do.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers