Bug#812609: Claiming #812609 and linking Salsa MR
harsh Kumar <[email protected]> Wed, 1 Apr 2026 03:10:50 +0530
| Newsgroups | gmane.linux.debian.devel.quality-assurance |
|---|---|
| Message-ID | <CABFVSYDs8UP=Wnh_Z6JPjvZk9fGEJOFt7r7c_NVKi=TQ12i=nw__21316.5890470677$1774993409$gmane$org@mail.gmail.com> |
--000000000000d79871064e58d208 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=E2=80=AFPM Lucas Nussbaum <[email protected]> w= rote: > 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' wi= th > > > 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=3Dhea= ds > > > > 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=3Dlucas%40debian.org&email2=3D&email= 3=3D&packages=3D&ignpackages=3D&format=3Dhtml&branches=3Don&gitlabci=3Don&g= bpconf=3Don&gitattributes=3Don&pipeline=3Don#results > > Lucas > --000000000000d79871064e58d208 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi Raphael and Lucas,<br><br><p style=3D"font-family:"= ;Google Sans Text",sans-serif;line-height:1.15;margin-top:0px">(CC'= ;ing my mentors, Santiago and Emmanuel, for visibility)</p><p style=3D"font= -family:"Google Sans Text",sans-serif;line-height:1.15;margin-top= :0px">Thank you both for these pointers! I wasn't aware that <code styl= e=3D"font-family:"Google Sans Text",sans-serif;line-height:1.15;m= argin-top:0px">vcswatch</code> and <code style=3D"font-family:"Google = Sans Text",sans-serif;line-height:1.15;margin-top:0px">UDD</code> were= already aggregating Salsa CI results to this extent.</p><p id=3D"gmail-p-r= c_ffc5ac3413c82d8e-208" style=3D"font-family:"Google Sans Text",s= ans-serif;line-height:1.15;margin-top:0px"><span style=3D"line-height:1.15;= margin-top:0px"><span class=3D"gmail-citation-404" style=3D"line-height:1.1= 5;margin-top:0px"></span></span><span style=3D"line-height:1.15;margin-top:= 0px"><span class=3D"gmail-citation-404" style=3D"line-height:1.15;margin-to= p:0px">Integrating this data into Distro Tracker is exactly what I had in m= ind for making CI status more visible to maintainers</span></span><span sty= le=3D"line-height:1.15;margin-top:0px"><span class=3D"gmail-citation-404 gm= ail-citation-end-404" style=3D"line-height:1.15;margin-top:0px"><span style= =3D"line-height:1.15;margin-top:0px"><sup class=3D"gmail-superscript" style= =3D"line-height:1.15;margin-top:0px;font-size:16px;background-color:transpa= rent"></sup></span></span></span><span style=3D"line-height:1.15;margin-top= :0px">. </span><span style=3D"line-height:1.15;margin-top:0px"><span class= =3D"gmail-citation-403" style=3D"line-height:1.15;margin-top:0px"></span></= span><span style=3D"line-height:1.15;margin-top:0px"><span class=3D"gmail-c= itation-403" style=3D"line-height:1.15;margin-top:0px">I will look into how= Distro Tracker currently consumes </span><code style=3D"font-family:"= Google Sans Text",sans-serif;line-height:1.15;margin-top:0px"><span cl= ass=3D"gmail-citation-403" style=3D"line-height:1.15;margin-top:0px">vcswat= ch</span></code><span class=3D"gmail-citation-403" style=3D"line-height:1.1= 5;margin-top:0px"> data and see how I can leverage that existing pipeline d= uring the </span><b style=3D"line-height:1.15;margin-top:0px"><span class= =3D"gmail-citation-403" style=3D"line-height:1.15;margin-top:0px">Community= Bonding phase (Weeks 1-3)</span></b><span class=3D"gmail-citation-403" sty= le=3D"line-height:1.15;margin-top:0px"> of my project</span></span><span st= yle=3D"line-height:1.15;margin-top:0px"><span class=3D"gmail-citation-403 g= mail-citation-end-403" style=3D"line-height:1.15;margin-top:0px"><span styl= e=3D"line-height:1.15;margin-top:0px"><sup class=3D"gmail-superscript" styl= e=3D"line-height:1.15;margin-top:0px;font-size:16px;background-color:transp= arent"></sup></span><span style=3D"line-height:1.15;margin-top:0px"><sup cl= ass=3D"gmail-superscript" style=3D"line-height:1.15;margin-top:0px;font-siz= e:16px;background-color:transparent"></sup></span><span style=3D"line-heigh= t:1.15;margin-top:0px"><sup class=3D"gmail-superscript" style=3D"line-heigh= t:1.15;margin-top:0px;font-size:16px;background-color:transparent"></sup></= span><span style=3D"line-height:1.15;margin-top:0px"><sup class=3D"gmail-su= perscript" style=3D"line-height:1.15;margin-top:0px;font-size:16px;backgrou= nd-color:transparent"></sup></span></span></span><span style=3D"line-height= :1.15;margin-top:0px">.</span></p><p></p><p id=3D"gmail-p-rc_ffc5ac3413c82d= 8e-209" style=3D"font-family:"Google Sans Text",sans-serif;line-h= eight:1.15;margin-top:0px"><span style=3D"line-height:1.15;margin-top:0px">= <span class=3D"gmail-citation-402" style=3D"line-height:1.15;margin-top:0px= "></span></span><span style=3D"line-height:1.15;margin-top:0px"><span class= =3D"gmail-citation-402" style=3D"line-height:1.15;margin-top:0px">This give= s me a much clearer path for the 'Integration' phase of my GSoC pro= posal</span></span><span style=3D"line-height:1.15;margin-top:0px"><span cl= ass=3D"gmail-citation-402 gmail-citation-end-402" style=3D"line-height:1.15= ;margin-top:0px"><span style=3D"line-height:1.15;margin-top:0px"><sup class= =3D"gmail-superscript" style=3D"line-height:1.15;margin-top:0px;font-size:1= 6px;background-color:transparent"></sup></span></span></span><span style=3D= "line-height:1.15;margin-top:0px">.<br>Thanks again for the technical steer= !<br><br><br><span style=3D"font-family:Arial,Helvetica,sans-serif">--</spa= n><br style=3D"font-family:Arial,Helvetica,sans-serif"><span style=3D"font-= family:Arial,Helvetica,sans-serif">Best regards,</span><br style=3D"font-fa= mily:Arial,Helvetica,sans-serif"><span style=3D"font-family:Arial,Helvetica= ,sans-serif">Harsh Kumar</span><br style=3D"font-family:Arial,Helvetica,san= s-serif"><span style=3D"font-family:Arial,Helvetica,sans-serif">IRC: @h4r-s= h:</span><a href=3D"http://matrix.org/" target=3D"_blank" style=3D"font-fam= ily:Arial,Helvetica,sans-serif">matrix.org</a><br style=3D"font-family:Aria= l,Helvetica,sans-serif"><span style=3D"font-family:Arial,Helvetica,sans-ser= if">Salsa: h4r-sh</span></span></p></div><br><div class=3D"gmail_quote gmai= l_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Mar 27, 20= 26 at 3:29=E2=80=AFPM Lucas Nussbaum <<a href=3D"mailto:[email protected]= ">[email protected]</a>> wrote:<br></div><blockquote class=3D"gmail_quote= " style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);= padding-left:1ex">On 27/03/26 at 09:21 +0100, Raphael Hertzog wrote:<br> > Hi,<br> > <br> > On Fri, 27 Mar 2026, harsh Kumar wrote:<br> > > Regarding the project link: I am applying for 'Improving Sals= a CI' with<br> > > Santiago. I contributed to Distro Tracker because my project visi= on<br> > > involves making Salsa CI data visible within the Tracker. However= , I<br> > <br> > That vision certainly makes sense. Showing CI results on the tracker i= s<br> > fully in spirit of what the tracker is about.<br> > <br> > vcswatch is already extracting CI results:<br> > <a href=3D"https://salsa.debian.org/qa/qa/-/tree/master/data/vcswatch?= ref_type=3Dheads" rel=3D"noreferrer" target=3D"_blank">https://salsa.debian= .org/qa/qa/-/tree/master/data/vcswatch?ref_type=3Dheads</a><br> > <br> > And distro-tracker already fetches the data from vcswatch, so it might= <br> > not be too hard to implement.<br> > <br> > > realize now that these are separate codebases with different stan= dards. I<br> > > will keep my GSoC focus on the Salsa CI Pipeline repository as in= structed<br> > > by the project guidelines.<br> > <br> > Ok. Up to you. I certainly welcome contributions to Distro Tracker too= :)<br> <br> Hi,<br> <br> UDD also has a salsa importer and dashboard that might be relevant<br> <a href=3D"https://udd.debian.org/salsa/?email1=3Dlucas%40debian.org&em= ail2=3D&email3=3D&packages=3D&ignpackages=3D&format=3Dhtml&= amp;branches=3Don&gitlabci=3Don&gbpconf=3Don&gitattributes=3Don= &pipeline=3Don#results" rel=3D"noreferrer" target=3D"_blank">https://ud= d.debian.org/salsa/?email1=3Dlucas%40debian.org&email2=3D&email3=3D= &packages=3D&ignpackages=3D&format=3Dhtml&branches=3Don&= ;gitlabci=3Don&gbpconf=3Don&gitattributes=3Don&pipeline=3Don#re= sults</a><br> <br> Lucas<br> </blockquote></div> --000000000000d79871064e58d208--