search

jenkins-infra / jenkins.io

A static site for the Jenkins automation server
https://jenkins.io
Other
323 stars 1.24k forks source link

[DOCS]: Adding curl as prerequisite for installation #6753

Open Viveksati5143 opened 1 year ago

Viveksati5143 commented 1 year ago

Describe your use-case which is not covered by existing documentation.

Keeping in mind https://github.com/jenkins-infra/jenkins.io/pull/6633 suggests for a 'curl' to 'wget' change, I suggest to add 'curl' as a prerequisite for installation in linux as It doesn't come pre-installed with linux & user has to manually install it using sudo snap install curl for the latest version.

Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.

image Should I create a pr for the same?

### Tasks
halkeye commented 1 year ago

Snap is very much an Ubuntu thing, it won't work on other distros. You'd want to use apt for debian based.

It's not a prerequisite of Jenkins. It might be worth noting that the documentation assumes it is installed. You could even bring up that you could use wget -O - instead of curl in that screenshot.

Viveksati5143 commented 1 year ago

Snap is very much an Ubuntu thing, it won't work on other distros. You'd want to use apt for debian based.

It's not a prerequisite of Jenkins. It might be worth noting that the documentation assumes it is installed. You could even bring up that you could use wget -O - instead of curl in that screenshot.

We can update it with sudo apt install curl as mentioned by @gounthar here

neerajmanivarnan commented 1 month ago

Can I work on this issue?

yashpal2104 commented 1 month ago

Here are my thoughts on this: 1) wget is for simple download: Just specify the URL, and it downloads the file. Recursive Downloads: Supports downloading entire websites or directories. But, it is limited to HTTP and FTP protocols (less versatile than curl). 2) curl It is more versatile and powerful, it is also used for transferring data with URLs. It supports a variety of protocols (HTTP, HTTPS, FTP, etc.). But, it is slightly more complex syntax for downloading files compared to wget. 3) Although this solution is less favourable one but we can - Optionally, provide examples for both tools in the documentation to accommodate different user preferences. ie use wget and curl both and let the user decide whether he wants to use wget or curl.