Link to install documentation instead of providing an incomplete copy

[MarkEWaite]

What feature do you want to see added?

The installation instructions on the pkg and mirror sites like:

• Debian weekly - pkg and mirrors
• Debian LTS - pkg and mirrors
• Red Hat Enterprise Linux weekly - pkg and mirrors
• Red Hat Enterprise Linux LTS - pkg and mirrors

are brief summaries of the more detailed instructions provided in the Linux section of the Installing chapter of the Jenkins User Handbook.

Those brief summaries lack the detailed information provided in the Linux section about Java requirements, hardware requirements, and operating system requirements. The brief summary of the Red Hat Enterprise Linux instructions recommends the rpm tool even though dnf is the default package manager on Fedora Linux. The brief summary of the Red Hat Enterprise Linux instructions uses an incorrect spelling ("Redhat") to refer to Red Hat Enterprise Linux and its derivatives. The brief summary of the Red Hat Enterprise Linux instructions does not mention the service control commands that are needed to start the service and enable the service.

Rather than having a brief and incomplete summary of the installation instructions on those the pkg and mirrors pages, I think that we should make the pkg and mirrors pages redirect to the jenkins.io site. A link already exists at the end of each of the pages, but making them redirect to the installation pages will take readers to the most complete instructions that we offer.

Upstream changes

No response

[hainenber]

Hi @MarkEWaite, I was very much new to the project so my conjecture could be wrong here, but if we need to redirect the pages at pkg.jenkins.io to www.jenkins.io/doc/book/installing/linux/, shouldn't it be configured in a repository handling the server behind pkg.jenkins.io?

I'm very glad to take this issue over, btw

[MarkEWaite]

Hi @MarkEWaite, I was very much new to the project so my conjecture could be wrong here, but if we need to redirect the pages at pkg.jenkins.io to www.jenkins.io/doc/book/installing/linux/, shouldn't it be configured in a repository handling the server behind pkg.jenkins.io?

I was hoping that we could use a redirect inside the top level web page rather than making that redirect at the web server level. However, I'm not an expert in the compromises that implies. I am open to either technique.

[hainenber]

That's an excellent suggestion! I'll soon make a PR to realize it. Thanks Mark!