Request for Status Update on Parasoft Findings Plugin 10.6.3 Release

[Yuqian Shi]

Hi,

This is Yuqian from Parasoft.

I attempted to release the Parasoft Findings Plugin 10.6.3 using "mvn release:prepare" and "mvn release:perform." Both commands were successful, and I created a corresponding tag:

https://github.com/jenkinsci/parasoft-findings-plugin/releases/tag/parasoft-findings-10.6.3

Could you kindly confirm the progress of this release? It's been two days since I initiated it, and I'd appreciate an update.

Thank you.

Best regards,

Yuqian Shi

[Gavin Mogan]

What are you expecting that didn't happen?

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/99eab28f-f544-4277-bc78-d6944c1c8549n%40googlegroups.com.

[Mark Waite]

As far as I can tell, you've created a release in GitHub but have not uploaded the binaries to the Jenkins artifact repository.  See the instructions at https://www.jenkins.io/doc/developer/publishing/releasing-manually/ for the steps that you need to perform in order to release manually.

Alternately, you could consider making the switch to automated release as described at https://www.jenkins.io/doc/developer/publishing/releasing-cd/

Mark Waite

[Daniel Beck]

On Fri, Sep 1, 2023 at 11:05 PM Mark Waite <mark.ea...@gmail.com> wrote:

On Friday, September 1, 2023 at 2:38:07 PM UTC-6 Yuqian wrote:

Hi,

This is Yuqian from Parasoft.

I attempted to release the Parasoft Findings Plugin 10.6.3 using "mvn release:prepare" and "mvn release:perform." Both commands were successful, and I created a corresponding tag:

https://github.com/jenkinsci/parasoft-findings-plugin/releases/tag/parasoft-findings-10.6.3

Could you kindly confirm the progress of this release? It's been two days since I initiated it, and I'd appreciate an update.

As far as I can tell, you've created a release in GitHub but have not uploaded the binaries to the Jenkins artifact repository.  See the instructions at https://www.jenkins.io/doc/developer/publishing/releasing-manually/ for the steps that you need to perform in order to release manually.

You uploaded 10.6.3-SNAPSHOT last Wednesday, and 10.6.4-SNAPSHOT now. No release commits exist in the repo either. Something about how you release is definitely wrong.

[Yuqian Shi]

I encountered an issue while attempting to release the last two times on the branch named "parasoft-findings-10.6.3," which matches the tag name. I've now changed the branch name to "parasoft-findings-10.6.3-branch" and successfully completed the 10.6.3 release. It seems there's a limitation when releasing on a branch with the same name as the tag.

Additionally, I unintentionally uploaded two snapshot artifacts, and I don't have the means to delete them. Could you please assist in removing these two snapshots?

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/y9n0Of_bKy8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2BRRM9v_NefSrCOGtauNj6GryT24qjd_tkjA76P73bRjQ%40mail.gmail.com.