Partially released plugin due to 403

[Egor]

Hello,

 

I’m releasing a new version of `aws-codepipeline` plugin by executing `mvn release:prepare release:perform`.

 

The command failed on attempt to upload JAR file:

 

```

[INFO] [INFO] ------------------------------------------------------------------------

[INFO] [INFO] BUILD FAILURE
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Total time:  18.079 s
[INFO] [INFO] Finished at: 2023-10-31T11:44:20-07:00
[INFO] [INFO] ------------------------------------------------------------------------

[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.1.0:deploy (default-deploy) on project aws-codepipeline: Failed to deploy artifacts: Could not transfer artifact com.amazonaws:aws-codepipeline:jar:0.47 from/to repo.jenkins-ci.org (https://repo.jenkins-ci.org/releases): status code: 403, reason phrase:  (403) -> [Help 1]

```

 

At the same time, I can see that 3 other files have been uploaded for the new release https://repo.jenkins-ci.org/releases/com/amazonaws/aws-codepipeline/0.47/. 

 

So, the new release directory contains just 3 files instead of 5.

 

Can it cause issues for the plugin users? If so, how can we fix that ?

 

--
Thank you,

Egor

[Basil Crow]

Have you read the instructions at
https://www.jenkins.io/doc/developer/publishing/releasing-manually/
which include making sure your plugin uses a reasonably up-to-date
parent POM? I created
https://github.com/jenkinsci/aws-codepipeline-plugin/pull/4 to try to
help with that. That document has two other pieces of troubleshooting
advice for 403 errors. If you still have problems after going through
all of that then you can create an issue at
https://github.com/jenkins-infra/helpdesk for an Artifactory
administrator to check your permissions.

[Egor]

Thank you for the response and PR, Basil.

If you don't mind, I have posted a comment with ask to exclude a commit from there before I merge.

Meanwhile, I confirmed that the newly released version of the plugin is available from the update center. Given that, are we good to keep the current 0.47 release as-is and incorporate your changes during the next release?