New Plugin version not updated on Jenkins IO Plugin page

[Ricardo DeLemos]

Hello,
I have released a new version of the plugin in GitHub (https://github.com/jenkinsci/crowdstrike-security-plugin) and I can see the new release there, but after waiting more than 6hr, I could not see the new release version in https://plugins.jenkins.io/crowdstrike-security/releases/

There was a error in the plugin version in the pom file, and that was corrected and the label moved to the correct commit, but there is no update on the plugin page.

How can I force the plugin page to get updated with the new version?

Thanks, 

Ricardo 

CONFIDENTIALITY NOTICE: The information contained in this message may be privileged and/or confidential. It is the property of CrowdStrike.  If you are not the intended recipient, or responsible for delivering this message to the intended recipient, any review, forwarding, dissemination, distribution or copying of this communication or any attachment(s) is strictly prohibited. If you have received this message in error, please notify the sender immediately, and delete it and all attachments from your computer and network.

[Mark Waite]

The 1.1.0 release is not available on repo.jenkins-ci.org.  https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/plugins/crowdstrike-security/ shows a 1.0.0 release that was delivered in 2022.  Since a tag has been created in the repository, I recommend that you declare the 1.1.0 release as "lost" and create a 1.2.0 release.

You'll need to run the maven release process, though I believe you'll first need to make some changes to your pom file.  The version in the pom should be 1.2.0-SNAPSHOT rather than 1.1.0, then when you run `mvn release:prepare release:perform` you'll choose the release as 1.2.0.

You can make your maintenance effort easier by modernizing the plugin by following the steps in the "Improve a plugin" tutorial.

Mark Waite

[Ricardo DeLemos]

Hi Mark,

I have created a new release (1.20) following your recommendation, but I still do not see the new release in https://plugins.jenkins.io/crowdstrike-security/releases/ . I have created a version 1.2.0, which I see on https://repo.jenkins-ci.org/releases/io/jenkins/plugins/crowdstrike-security/. I do not see a 1.2.0-SNAPSHOT in https://repo.jenkins-ci.org/snapshots/io/jenkins/plugins/crowdstrike-security/.

I have tried again, creating a 1.2.1 release, and got the same result. This was the versions set on the pom on the release 1.2.0

<scm>

...

<tag>crowdstrike-security-1.2.0</tag>

</scm>

<version>1.2.0</version>

<dependencyManagement>

<dependencies>

<dependency>

<groupId>io.jenkins.tools.bom</groupId>

<artifactId>bom-2.332.x</artifactId>

<version>1210.vcd41f6657f03</version>

<type>pom</type>

<scope>import</scope>

</dependency>

</dependencies>

</dependencyManagement>

<properties>

<revision>1.0.0</revision>

...

</properties>

[Mark Waite]

On Wednesday, July 12, 2023 at 8:57:48 PM UTC-6 Ricardo DeLemos wrote:

Hi Mark,

I have created a new release (1.20) following your recommendation, but I still do not see the new release in https://plugins.jenkins.io/crowdstrike-security/releases/ . I have created a version 1.2.0, which I see on https://repo.jenkins-ci.org/releases/io/jenkins/plugins/crowdstrike-security/. I do not see a 1.2.0-SNAPSHOT in https://repo.jenkins-ci.org/snapshots/io/jenkins/plugins/crowdstrike-security/.

I have tried again, creating a 1.2.1 release, and got the same result. This was the versions set on the pom on the release 1.2.0

<scm>

...

<tag>crowdstrike-security-1.2.0</tag>

</scm>

<version>1.2.0</version>

<dependencyManagement>

<dependencies>

<dependency>

<groupId>io.jenkins.tools.bom</groupId>

<artifactId>bom-2.332.x</artifactId>

<version>1210.vcd41f6657f03</version>

<type>pom</type>

<scope>import</scope>

</dependency>

</dependencies>

</dependencyManagement>

<properties>

<revision>1.0.0</revision>

...

</properties>

I see https://plugins.jenkins.io/crowdstrike-security/ showing 3 releases, 1.0.0, 1.2.0, and 1.2.1.  I assume that means all is OK for you?

Mark Waite

[Ricardo DeLemos]

Yes. The 2 versions (1.2.0 and 1.2.1) showed up 15 minutes after I have send you the previous email. It is all set now.

Just for reference on the next update: the 1.2.0 version took over 6hr to show up on https://plugins.jenkins.io/, while 1.2.1 showed up after 1 hr. It is just the time that the batch process ran to update the wiki page (~ 6 hours)?

Thanks for your help!

-Ricardo

[Mark Waite]

On Wednesday, July 12, 2023 at 10:04:55 PM UTC-6 Ricardo DeLemos wrote:

Yes. The 2 versions (1.2.0 and 1.2.1) showed up 15 minutes after I have send you the previous email. It is all set now.

Just for reference on the next update: the 1.2.0 version took over 6hr to show up on https://plugins.jenkins.io/, while 1.2.1 showed up after 1 hr. It is just the time that the batch process ran to update the wiki page (~ 6 hours)?

No, that's just the "luck of the draw" for the times when the plugins site is rebuilt.  I believe it is rebuilt approximately every 6 hours.

 

[Ricardo DeLemos]

OK. Thanks!