[continued from previous message]
the pipeline and project, and then we fetch its status once an hour to
determine the final state and record the stats. So all the public pipelines
that use Salsa CI with `SALSA_CI_ENABLE_STATS` flag ON (currently enabled
by default), will be registered.
Quoting Johannes (or Josch :),
> Could you please remove these lines? The dashboard seems to work fine even
> when instructing my adblocker to not send my data to google.
Hah, nice catch! Those lines are for the Urbanist font we use on the
website. I€€€m not entirely sure if they send any data to Google, but
I€€€ll go
ahead and remove the links and add the font to the assets instead. Thanks
for pointing it out!
PS.: The issue tracker is at
https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/413.
Thanks so much, everyone! ^^
Aayush Raj
GSoC student mentored by Otto Kek€€l€€inen
On Mon, 1 Sept 2025 at 17:36, Alexander Wirt wrote:
> Am Mon, Sep 01, 2025 at 02:00:00PM +0200 schrieb Lucas Nussbaum:
> > On 01/09/25 at 12:56 +0200, Alexander Wirt wrote:
> > > Am Fri, Aug 29, 2025 at 01:03:19PM +0200 schrieb Alexander Wirt:
> > > > Am Fri, Aug 29, 2025 at 06:05:12AM +0530 schrieb Aayush Raj:
> > > > > Greetings folks!
> > > > >
> > > > > I wanted to announce that salsa-status.debian.net is now up and
> running!
> > > > >
> > > > > This Status Page provides both Salsa CI users and the Salsa CI
> developer
> > > > > team with visibility into CI performance, helping identify wasteful
> > > > > practices, broken configurations, and optimization opportunities
> across the
> > > > > entire Debian package ecosystem.
> > > > >
> > > > > One of the main objectives is to help catch wasteful CI usage,
> which hasn't
> > > > > been possible/easy before due to lack of overview/stats.
> > > > >
> > > > > *The main features of the Salsa CI status page are:*
> > > > >
> > > > > -
> > > > >
> > > > > Real-time Pipeline Monitoring: Pipeline stats, success rates,
> > > > > performance trends, and related metrics.
> > > > > -
> > > > >
> > > > > Project Analytics: Detailed insights into projects€€€ CI history
> and
> > > > > configurations
> > > > > -
> > > > >
> > > > > Job Type Analysis: Insights into types of jobs running in and
> on top of
> > > > > Salsa CI
> > > > > -
> > > > >
> > > > > CI Stats & Performance: CI duration trends and resource
> consumption
> > > > > -
> > > > >
> > > > > Matrix Alerts - Automated notifications for performance
> degradation at
> > > > > https://matrix.to/#/#salsa-stats:matrix.org
> > > >
> > > > Which api endpoint do you scrape and how often?
> > > Ping?
> >
> > Hi Alex,
> >
> > AFAIK€€€, the CI pipeline provided by the salsa-ci-team team€€€ is
> > instrumented to collect data. See
> >
> https://salsa.debian.org/salsa-ci-team/pipeline/-/blob/master/
alsa-ci.yml?ref_type=heads#L223
> >
> > That's why people are rightfully saying that the name is not correct and
> > should be salsa-ci-stats.debian.net (or even
> > salsa-ci-team-pipeline-stats.debian.net)
> >
> > I suppose that when the statistics collector endpoint learns about a
> > pipeline, then it polls salsa about that pipeline's status.
> >
> > Lucas
> >
> > €€€ I'm not involved with status-status.d.n
> > €€€ https://salsa.debian.org/salsa-ci-team/pipeline
>
> That is useful information, but in the end leaves me with even more
> questions. I really want to have an
> answer to my questions. Otherwise it may happen that we just block the
> service.
>
> Alex
>
>
[continued in next message]
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
