We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
N/A
Ubuntu 22.04.1 LTS x86_64
Visit https://ci.jenkins.io/job/Packaging/job/packaging/job/master/lastSuccessfulBuild/ and look at the names of the build artifacts.
The names shouldn't have the logical flaws described below in the Actual Results section.
This repository produces three (3) artifacts, e.g.
jenkins_2.373_all.deb
jenkins-2.373-1.1.noarch.rpm
jenkins-2.373-1.2.noarch.rpm
The first of these is obviously a Debian package, but it is not obvious that the second is for Red Hat systems and the third is for openSUSE systems, resulting in awkward downstream workarounds like https://github.com/jenkinsci/jenkins/blob/47322f3da67d29380ec7f16381f32d1f0cf9472f/.github/workflows/publish-release-artifact.yml#L201-L202. Furthermore, the version numbers "1.1" and "1.2" make no sense: why would the same source code yield two different versions?
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Jenkins and plugins versions report
Environment
N/A
What Operating System are you using (both controller, and any agents involved in the problem)?
Ubuntu 22.04.1 LTS x86_64
Reproduction steps
Visit https://ci.jenkins.io/job/Packaging/job/packaging/job/master/lastSuccessfulBuild/ and look at the names of the build artifacts.
Expected Results
The names shouldn't have the logical flaws described below in the Actual Results section.
Actual Results
This repository produces three (3) artifacts, e.g.
jenkins_2.373_all.debjenkins-2.373-1.1.noarch.rpmjenkins-2.373-1.2.noarch.rpmThe first of these is obviously a Debian package, but it is not obvious that the second is for Red Hat systems and the third is for openSUSE systems, resulting in awkward downstream workarounds like https://github.com/jenkinsci/jenkins/blob/47322f3da67d29380ec7f16381f32d1f0cf9472f/.github/workflows/publish-release-artifact.yml#L201-L202. Furthermore, the version numbers "1.1" and "1.2" make no sense: why would the same source code yield two different versions?
Anything else?
No response
The text was updated successfully, but these errors were encountered: