Add permission file for fips-bundle-test

[olamy]

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:

• @olamy
• @jtnord

This 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)

Beta Give feedback

1. The usernames of the users added to the "developers" section in the .yml file are the same the users use to log in to accounts.jenkins.io.
2. All users added have logged in to Artifactory and Jira once.
3. I have mentioned an existing team member of the plugin or component team to approve this request.

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)

Beta Give feedback

1. I have provided a link to the pull request in my plugin, which enables CD according to the documentation.

Reviewer checklist

Beta Give feedback

1. Check that the $pluginId Developers team has Admin permissions while granting the access.
2. In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
3. If security contacts are changed (this includes add/remove), ping the security officer (currently @Wadeck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it.

[jtnord]

would be nice to have CD from the start though :)

[olamy]

would be nice to have CD from the start though :)

sure let's make some marketing for GHA...

657b3d7

[daniel-beck]

CD hasn't been properly set up, there's now a -rcwhatever release. That's why there's a checklist item specifically for CD enablement 😉

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.

[olamy]

hopefully should be fixed here jenkinsci/lib-fips-bundle-test#2

[olamy]

this is fixed but the first release will break dependabot :(

https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/test/fips/lib-fips-bundle-test/-rc16.e95456a_916d7/

I can see solutions:

• change the artifactId to fips-bundle-test (as mentioned here Name has been changed from the original repo #4085 (comment))
• delete the release -rc16.e95456a_916d7 from artifactory (I hope this will cleanup metadata.xml
• another solution?

[timja]

Change the artifact id would be the smoothest I think

[olamy]

done here #4089

[olamy]

@timja thanks for your patience!