Fix fips-bundle-test artifactId (it is for github repo lib-fips-bundle-test, looks confusing but in fact it's not :) #4089
Conversation
…e-test, looks confusing but in fact it's not :) Signed-off-by: Olivier Lamy <olamy@apache.org>
| @@ -2,7 +2,7 @@ | |||
| name: "lib-fips-bundle-test" | |||
| github: "jenkinsci/lib-fips-bundle-test" | |||
| paths: | |||
| - "io/jenkins/test/fips/lib-fips-bundle-test" | |||
There was a problem hiding this comment.
weird
Caused by: org.apache.maven.wagon.authorization.AuthorizationException: authorization failed for https://repo.jenkins-ci.org/releases/io/jenkins/test/fips/fips-bundle-test/20.vb_e5df22f62ea_/fips-bundle-test-20.vb_e5df22f62ea_.pom, status: 403 Forbidden
here https://github.com/jenkinsci/lib-fips-bundle-test/actions/runs/10845721879/job/30097173717
There was a problem hiding this comment.
oh maybe I need to learn patience? :)
There was a problem hiding this comment.
should run quick but the job does take a bit of time: https://github.com/jenkins-infra/repository-permissions-updater/blob/master/Jenkinsfile#L16
There was a problem hiding this comment.
no worries, Friday arvo I will have a beer ;)
There was a problem hiding this comment.
I got few but still a problem (not sure I can get more now :) )
I will wait tomorrow.
There was a problem hiding this comment.
There was a problem hiding this comment.
I hope there is no mistake somewhere as I may have been confused by the naming convention :)
- github is
lib-fips-bundle-test - artifactId
fips-bundle-test - file here is
component-fips-bundle-test.yml
You guys made it hard to me to not make any mistake :)
There was a problem hiding this comment.
issue created here jenkins-infra/helpdesk#4290
Signed-off-by: Olivier Lamy olamy@apache.org
Link to GitHub repository
When modifying release permission
List the GitHub usernames of the users who should have commit permissions below:
@username1@username2This is needed in order to cut releases of the plugin or component.
If you are modifying the release permission of your plugin or component, fill out the following checklist:
Release permission checklist (for submitters)
When enabling automated releases (cd: true)
Follow the documentation to ensure, your pull request is set up properly. Don't merge it yet.
In case of changes requested by the hosting team, an open PR facilitates future reviews, without derailing work across multiple PRs.
Link to the PR enabling CD in your plugin
CD checklist (for submitters)
Reviewer checklist
There are IRC Bot commands for it.