sonar-quality-gates-plugin release

[Kirk Fitzsimons]

Hi all,

I accidentally published a GitHub Release tagged next for the sonar-quality-gates-plugin.

Because the tag is not a valid incrementals version, CD did not produce a proper plugin release.

Repository: jenkinsci/sonar-quality-gates-plugin

Plugin page: Sonar Quality Gates Plugin

As a result, GitHub currently shows “next” as the latest release, but this isn’t a usable plugin version.

How can i fix this on github and produce a proper release? I have done created proper releases before with code changes/bug fixes, but this draft release was just dependabot changes which i merged in, what did i miss? A tag on the Pr?

Thanks,

[Jenkins Developers]

The GitHub tag for "next" does not seem to have reached the Jenkins artifact repository.

https://updates.jenkins.io/latest/sonar-quality-gates.hpi?mirrorlist shows that the most recent release is 352.vdcdb_d7994fb_6.

The Jenkins artifact repository at https://repo.jenkins-ci.org/artifactory/releases/org/jenkins-ci/plugins/sonar-quality-gates/ does not have a release named "next".

You can delete the GitHub release for "next" and can delete the tag for "next".

If you apply the label `developer` or `enhancement` to the open pull request https://github.com/jenkinsci/sonar-quality-gates-plugin/pull/78 and merge it, then that should generate a new release using the expected version number scheme.

Mark Waite