Hi!

The grml.org project has been hosting Jenkins jobs for dpkg for a long
time now, as the very initial CI we had. The jobs also generate a repo
so that people can run the latest code from git main, with the
following apt config:

deb https://jenkins.grml.org/debian dpkg main

Due to security issues in Jenkins or continuous attacks (AFAIR/AFAIUI)
its web interface at https://jenkins.grml.org/ has been firewalled, so
it now becomes a bit cumbersome to diagnose issues that happen there
w/o having to bother someone.

I've talked about this briefly with Mika, and I while I hugely appreciate
the service that has been provided over the years (thanks Mika!), I'm
thinking it's probably time to permanently disable it (I did this the
other day as a temporary measure to stop spamming the list) given the availability of more self-service CI systems that do not require
burdening other people, such as the one currently used from salsa (or
perhaps one from codeberg). I think the main blocker might be whether
anyone is still using that repo?

If so, I guess we could generate one from the salsa CI too? Otherwise
I'll probably consider permanently disabling the Jenkins triggers from
the dpkg.org side and ask Mika to remove the Jenkins jobs and clean up
that repo. Objections?

Thanks,
Guillem

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi!

On Thu, 2024-03-14 at 00:19:09 +0100, Alexandre Detiste wrote:

Le sam. 9 mars 2024 à 18:29, Guillem Jover <guillem@debian.org> a écrit :

The grml.org project has been hosting Jenkins jobs for dpkg for a long
time now, as the very initial CI we had. The jobs also generate a repo
so that people can run the latest code from git main, with the
following apt config:

deb https://jenkins.grml.org/debian dpkg main

Due to security issues in Jenkins or continuous attacks (AFAIR/AFAIUI)
its web interface at https://jenkins.grml.org/ has been firewalled, so
it now becomes a bit cumbersome to diagnose issues that happen there
w/o having to bother someone.

I've talked about this briefly with Mika, and I while I hugely appreciate the service that has been provided over the years (thanks Mika!), I'm thinking it's probably time to permanently disable it (I did this the
other day as a temporary measure to stop spamming the list) given the availability of more self-service CI systems that do not require
burdening other people, such as the one currently used from salsa (or perhaps one from codeberg). I think the main blocker might be whether anyone is still using that repo?

If so, I guess we could generate one from the salsa CI too? Otherwise
I'll probably consider permanently disabling the Jenkins triggers from
the dpkg.org side and ask Mika to remove the Jenkins jobs and clean up
that repo. Objections?

Nobody did answered.

Besides you that is. :)

I could have used "deb https://jenkins.grml.org/debian dpkg main"
but it seems a lot of work to maintain compared to my little use.

So, Mika, I guess it's time to disable and remove the jobs from Jenkins?
Unless perhaps there are stats showing lots of usage for that repo (which
I'd doubt)? Although I don't think this is urgent at all.

Thanks,
Guillem

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi!

* Guillem Jover [Fri Apr 26, 2024 at 09:57:09AM +0200]:

On Thu, 2024-03-14 at 00:19:09 +0100, Alexandre Detiste wrote:

Le sam. 9 mars 2024 à 18:29, Guillem Jover <guillem@debian.org> a écrit :

The grml.org project has been hosting Jenkins jobs for dpkg for a long time now, as the very initial CI we had. The jobs also generate a repo
so that people can run the latest code from git main, with the
following apt config:

deb https://jenkins.grml.org/debian dpkg main

Due to security issues in Jenkins or continuous attacks (AFAIR/AFAIUI) its web interface at https://jenkins.grml.org/ has been firewalled, so
it now becomes a bit cumbersome to diagnose issues that happen there
w/o having to bother someone.

I've talked about this briefly with Mika, and I while I hugely appreciate the service that has been provided over the years (thanks Mika!), I'm thinking it's probably time to permanently disable it (I did this the other day as a temporary measure to stop spamming the list) given the

[...]

I could have used "deb https://jenkins.grml.org/debian dpkg main"
but it seems a lot of work to maintain compared to my little use.

So, Mika, I guess it's time to disable and remove the jobs from Jenkins?

Perfectly fine for me :)

Unless perhaps there are stats showing lots of usage for that repo (which
I'd doubt)? Although I don't think this is urgent at all.

Nowadays there's only very little usage of it AFAICS, so I think it
makes sense to retire the service. Thanks for reaching out, I'll
take care of disabling and removing it.

regards
-mika-

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEM8yxNkAa/shDo4djlqh4crfqNzcFAmYrYa0ACgkQlqh4crfq Nzc6axAArAEHv7Dis+4ZeCJ0nKd84GlxqCnm5Z4SQ0BJKSDoyybjyxeuXb7T0s3N rL3ABQPjJZzejLPh5IANV6HEjXT9T3+AF1mVm2p3Hm6osJ9fT152S45l9gs9xQFX 5oraJTDPNG0e3UZhhcU/VO/CPQg5lDesD/iTA699Walw3m7gd3xZL+G9LPiYZcDV guM7W77wTGrgFBK6+sVLu2lZJlN+ApCflqjDfnUzKmMmaeBwBJrboYWrCdYRUSV+ TB5toqqzbzxLSL/gGdN401iuETn2/mGI2BJ1J8aRQarQrNt0ZuxWNl14yAwK02y7 3T5jzhfQFGFjGHoSGwD8VWfbA7TvW4dc3vQnBHQ+s8j5qeJ0GSM0hiRJ6QQFo+eG vp8COX9VfJgw+3XzYIoRNW/FWFUKi3v88BuaxcVu7cIRpw2fcB+F5HLDRlOSFMJL jLSud3mdoNasuHuzxroHXmRIpDH4TQ5iAhrc+zjDmlv2GgfDnmmT9c8l2f7V+wZf g1BBFByTjckYmNcCLE3r/rh5NUEp1ByVDux6wvGenQn/dkH8rQn3j5EMtYwvIf1q XyfPI6ZgmjtrGTUt1qb4bZ7aietAA/nJGSdBIucV757u/hb9UpAigDjb7Aj6dCBX tT8/3SMs6kqm83vluTvbLF0rubV+W8EnYFyIVkeK4Vhwvlpv+r0=
=WhUg
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)