Why do the yum repos for stable and dev Jenkins not have older releases?

[Nico Kadel-Garcia]

I run into people with running Jenkins who are not prepared to jump to the latest LTS release when installing a new server, but the previous RPMs are no longer in the redat-stable re[p at https://pkg.jenkins.io/rpm-stable . or the dev repo at https://pkg.jenkins.io/rpms . Was there a reason for that? And are the old RPMs available online anywhere for reference? I'll hate to have to keep a mirror up-to-date and manage it internally for them.

[Mark Waite]

On Thu, Apr 2, 2026 at 6:02 PM Nico Kadel-Garcia <nka...@gmail.com> wrote:

I run into people with running Jenkins who are not prepared to jump to the latest LTS release when installing a new server, but the previous RPMs are no longer in the redat-stable re[p at https://pkg.jenkins.io/rpm-stable . or the dev repo at https://pkg.jenkins.io/rpms . Was there a reason for that?

Yes, there was.  As noted in the Jenkins weekly 2.537 changelog and the Jenkins 2.541.1 upgrade guide, the Red Hat and openSUSE RPM packages have been unified into a single RPM package, with automatic redirection for smooth upgrades.

 

And are the old RPMs available online anywhere for reference?

The old weekly packages are available from https://pkg.jenkins.io/redhat-legacy/ for Red Hat distributions and from https://pkg.jenkins.io/opensuse-legacy/ for openSUSE distributions.  The old LTS packages are available from https://pkg.jenkins.io/redhat-stable-legacy/ Red Hat distributions and from https://pkg.jenkins.io/opensuse-stable-legacy/ for openSUSE distributions.

You can also refer to https://github.com/jenkinsci/jenkins/issues/26206 and https://github.com/jenkinsci/jenkins/issues/26156 for more details.

Mark Waite

 

[Nico Kadel-Garcia]

Good morning. And thank you.

Unification is not the point for people I deal with, it's access to
the legacy packages.

So I'm staring at three repos:

Dev: https://pkgs.jenkins.io/rpm
LTS: https://pkgs.jenkins.io//redhat-stable
Archive: https://pkgs.jenkins.io/redhat-stable-legacy

I'm slightly appalled by the confusing directories for the repos, and
by all of the published "jenkins.repo" calling the yum repo "jenkins"
for all these locations. But I can work from those....

> --
> You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGps6YTczkHw0KcXYRfL7iiO2hmg3RRuGbSr9Em06tShg%40mail.gmail.com.

[Nico Kadel-Garcia]

And the "legacy repo".... isn't a repo. It's merely a web page with a
list, but without repodata with which to keep it synchronized. To get
the RPM file names, you either have to pull them out of the web page,
or deduce them from he git tags.

That's not *exactly* what I was looking for, due to some older Jenkins
users, though I can understand the temptation to cut off easy
deployment for the older releases.

[Mark Waite]

On Thu, Apr 9, 2026 at 5:31 PM Nico Kadel-Garcia <nka...@gmail.com> wrote:

And the "legacy repo".... isn't a repo. It's merely a web page with a
list, but without repodata with which to keep it synchronized.  To get
the RPM file names, you either have to pull them out of the web page,
or deduce them from he git tags.

I don't understand why you say that the legacy repo is not a repo.

https://pkg.jenkins.io/redhat-stable-legacy/jenkins.repo has the expected content.

I used the following commands to install Jenkins 2.528.3 on Rocky Linux 9:

sudo wget -O /etc/yum.repos.d/jenkins.repo https://pkg.jenkins.io/redhat-stable-legacy/jenkins.repo

sudo dnf -y --nogpgcheck install jenkins

I had to skip the GPG check from the dnf command because the GPG key of repository has expired.

Mark Waite

[Nico Kadel-Garcia]

On Thu, Apr 9, 2026 at 7:54 PM Mark Waite <mark.ea...@gmail.com> wrote:
>
> On Thu, Apr 9, 2026 at 5:31 PM Nico Kadel-Garcia <nka...@gmail.com> wrote:
>>
>> And the "legacy repo".... isn't a repo. It's merely a web page with a
>> list, but without repodata with which to keep it synchronized. To get
>> the RPM file names, you either have to pull them out of the web page,
>> or deduce them from he git tags.
>
>
> I don't understand why you say that the legacy repo is not a repo.
>
> https://pkg.jenkins.io/redhat-stable-legacy/jenkins.repo has the expected content.

Ahh. The misleadingly named "jenkins.repo" file you pointed is
internally named "jenkins-stable" internally, which overlaps with the
*other* mislabeled jenkins.repo file at
https://pkg.jenkins.io/rpm-stable/jenkins.repo .

It's confusing and triggers overwriting other files to give them all
the same filename and the same top stanza of:

[Jenkins]
name=jenkins-stable

The .repo files get interpreted at the time "rpm" is run, and the
contents of the files commingled even if stored separately. The
practice is misleading. Please, label the primary Jenkins file as
"jenkins-stable" in a file called "jenkins-stable.repo", and
corresponding .repo filea with matching names, to avoid this cnfusion.

> I used the following commands to install Jenkins 2.528.3 on Rocky Linux 9:
>
> sudo wget -O /etc/yum.repos.d/jenkins.repo https://pkg.jenkins.io/redhat-stable-legacy/jenkins.repo
> sudo dnf -y --nogpgcheck install jenkins
>
> I had to skip the GPG check from the dnf command because the GPG key of repository has expired.
>
> Mark Waite
>

> --
> You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

> To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFw5yYTAzHv5unLC_cBOchbRUB8XrkjVYJ5Prefhgnnhw%40mail.gmail.com.