Release 2.12.12 incomplete (JAR file not published)

[dduportal]

Hello there 👋

The last release 2.12.12 does not have a JAR file attachement like previous versions, causing build errors in downstream PR jenkinsci/docker#1667 which relies on downloading the published artefact.

It comes from an incomplete release: the GitHub action "Publish" triggered by the release/tag creation failed with the error Unable to resolve action actions/upload-asset, repository not found

The action upload-release-asset is archived, which explains why it's failing.

[dduportal]

Proposal : I'm gonna open a PR to switch using the gh command line inb the publish process, as there are no certified GitHub action (and using a 3rd party is a bit weird for this )

[dduportal]

@MarkEWaite @timja I'm not maintainer here, may I ask you to:

• Upload manually the JAR file (with the proper naming) to the current 2.12.12
• Review chore(GHA) use gh CLI to publish artefact to release #578 so we can test a 2.12.13 release

?

[timja]

Upload manually the JAR file (with the proper naming) to the current 2.12.12

I would rather test while we are in context rather than months later 😄

[timja]

Looks like it worked? https://github.com/jenkinsci/plugin-installation-manager-tool/releases/tag/2.12.13

[dduportal]

Upload manually the JAR file (with the proper naming) to the current 2.12.12

I would rather test while we are in context rather than months later 😄

I don't mind a new release at all (I also aimed at a new 2.12.13 with my PR, but that let a "broken" release in the GitHub release history while the artifactory history has it.

[dduportal]

Looks like it worked? https://github.com/jenkinsci/plugin-installation-manager-tool/releases/tag/2.12.13

Yep, victory \o/ I'm closing the issue, I let the maintainers judge of if it is worth uploading the 2.12.12 or not :)

Thanks!

[timja]

not worth it to me it's superseded by the new one

[MarkEWaite]

I would prefer to upload the 2.12.12 artifact for consistency and am happy to be the maintainer that does it. However, I can't find that artifact on https://repo.jenkins-ci.org . I also can't find the 2.12.13 artifact on repo.jenkins-ci.org .

I see plugin-management-cli in the https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/plugin-management/ but I don't see the jenkins-plugin-manager-x.xx.xx.jar file on repo.

The jenkins-plugin-manager-x.xx.xx.jar Main class has a fully qualified class io.jenkins.tools.pluginmanager.cli.Main yet https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/tools/ shows that there is no directory for pluginmanager under io.jenkins.tools.

Can someone help me with my weak Artifactory search skills?

[dduportal]

I would prefer to upload the 2.12.12 artifact for consistency and am happy to be the maintainer that does it. However, I can't find that artifact on https://repo.jenkins-ci.org . I also can't find the 2.12.13 artifact on repo.jenkins-ci.org .

I see plugin-management-cli in the https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/plugin-management/ but I don't see the jenkins-plugin-manager-x.xx.xx.jar file on repo.

The jenkins-plugin-manager-x.xx.xx.jar Main class has a fully qualified class io.jenkins.tools.pluginmanager.cli.Main yet https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/tools/ shows that there is no directory for pluginmanager under io.jenkins.tools.

Can someone help me with my weak Artifactory search skills?

If you look at the release process workflow file (https://github.com/jenkinsci/plugin-installation-manager-tool/blob/c795ccd05c0c48b9dc624eb82511331acbe12fff/.github/workflows/publish-release-artifact.yml) you'll see on the line 32 that it downloads the jar file from JFrog.

As per

plugin-installation-manager-tool/.github/workflows/publish-release-artifact.yml

Line 27 in c795ccd

ARTIFACT_ID=plugin-management-cli

, it's the plugin-management-cli artefact.

E.g. from https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/plugin-management/plugin-management-cli/2.12.12/ for this release.

@MarkEWaite is that ok for you?

[MarkEWaite]

If you look at the release process workflow file (https://github.com/jenkinsci/plugin-installation-manager-tool/blob/c795ccd05c0c48b9dc624eb82511331acbe12fff/.github/workflows/publish-release-artifact.yml) you'll see on the line 32 that it downloads the jar file from JFrog.

As far as I can tell, the jar file that it downloads (https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/plugin-management/plugin-management-cli/2.12.12/plugin-management-cli-2.12.12.jar) is then packaged with an additional Java class and that is used to create the delivered jar file, I am unable to find an archive of the delivered jar file

[dduportal]

If you look at the release process workflow file (https://github.com/jenkinsci/plugin-installation-manager-tool/blob/c795ccd05c0c48b9dc624eb82511331acbe12fff/.github/workflows/publish-release-artifact.yml) you'll see on the line 32 that it downloads the jar file from JFrog.

As far as I can tell, the jar file that it downloads (https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/plugin-management/plugin-management-cli/2.12.12/plugin-management-cli-2.12.12.jar) is then packaged with an additional Java class and that is used to create the delivered jar file, I am unable to find an archive of the delivered jar file

The release process "only" uploads (as attachement to the freshly published GitHub release) the file downloaded with wget:

plugin-installation-manager-tool/.github/workflows/publish-release-artifact.yml

Line 38 in c795ccd

run: gh release upload ${{ steps.set-version.outputs.project-version }} ./${{ steps.fetch-artifact.outputs.file-name }}-${{ steps.set-version.outputs.project-version }}.jar

[MarkEWaite]

Thanks for the explanation. Now I understand. The plugin-management-cli-2.12.12.jar downloaded from repo is renamed to jenkins-plugin-manager-2.12.12.jar and uploaded to GitHub.