Bug#812609: Claiming #812609 and linking Salsa MR

Hi,

it might be useful to mention that the UDD implementation is a bit more
low level, since it just fetches the JSON API response for the latest
pipeline (and its jobs) for the default branch of each salsa project
used for Debian packaging.

Analyzing the pipeline and jobs statuses is done when the dashboard is
rendered. See https://salsa.debian.org/qa/udd/-/blob/master/web/inc/dmd-data.rb?ref_type=heads#L530

So depending on what you want to achieve, it might be better to use the
more high-level vcswatch data, or the more low-level UDD data (and build
your own analysis of the data).

The UDD data should be available on the UDD public mirror as well if you
want to do SQL directly.

Lucas


On 01/04/26 at 03:10 +0530, harsh Kumar wrote:
> Hi Raphael and Lucas,
> 
> (CC'ing my mentors, Santiago and Emmanuel, for visibility)
> 
> Thank you both for these pointers! I wasn't aware that vcswatch and UDD
> were already aggregating Salsa CI results to this extent.
> 
> Integrating this data into Distro Tracker is exactly what I had in mind for
> making CI status more visible to maintainers. I will look into how Distro
> Tracker currently consumes vcswatch data and see how I can leverage that
> existing pipeline during the *Community Bonding phase (Weeks 1-3)* of my
> project.
> 
> This gives me a much clearer path for the 'Integration' phase of my GSoC
> proposal.
> Thanks again for the technical steer!
> 
> 
> --
> Best regards,
> Harsh Kumar
> IRC: @h4r-sh:matrix.org
> Salsa: h4r-sh
> 
> On Fri, Mar 27, 2026 at 3:29 PM Lucas Nussbaum <[email protected]> wrote:
> 
> > On 27/03/26 at 09:21 +0100, Raphael Hertzog wrote:
> > > Hi,
> > >
> > > On Fri, 27 Mar 2026, harsh Kumar wrote:
> > > > Regarding the project link: I am applying for 'Improving Salsa CI' with
> > > > Santiago. I contributed to Distro Tracker because my project vision
> > > > involves making Salsa CI data visible within the Tracker. However, I
> > >
> > > That vision certainly makes sense. Showing CI results on the tracker is
> > > fully in spirit of what the tracker is about.
> > >
> > > vcswatch is already extracting CI results:
> > >
> > https://salsa.debian.org/qa/qa/-/tree/master/data/vcswatch?ref_type=heads
> > >
> > > And distro-tracker already fetches the data from vcswatch, so it might
> > > not be too hard to implement.
> > >
> > > > realize now that these are separate codebases with different
> > standards. I
> > > > will keep my GSoC focus on the Salsa CI Pipeline repository as
> > instructed
> > > > by the project guidelines.
> > >
> > > Ok. Up to you. I certainly welcome contributions to Distro Tracker too :)
> >
> > Hi,
> >
> > UDD also has a salsa importer and dashboard that might be relevant
> >
> > https://udd.debian.org/salsa/?email1=lucas%40debian.org&email2=&email3=&packages=&ignpackages=&format=html&branches=on&gitlabci=on&gbpconf=on&gitattributes=on&pipeline=on#results
> >
> > Lucas
> >