Skip to content

Conversation

@simonelbaz
Copy link
Contributor

Link to GitHub repository

https://github.com/jenkinsci/openstack-cloud-plugin

When modifying release permission

List the GitHub usernames of the users who should have commit permissions below:

  • @simonelbaz

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)

  • 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.
  • All users added have logged in to Artifactory and Jira once.
  • 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

jenkinsci/openstack-cloud-plugin#393

CD checklist (for submitters)

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

Reviewer checklist

  • Check that the $pluginId Developers team has Admin permissions while granting the access.
  • In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
  • 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.

@simonelbaz simonelbaz requested a review from a team as a code owner March 6, 2025 16:30
@MarkEWaite MarkEWaite changed the title Update plugin-openstack-cloud.yml Adopt plugin-openstack-cloud Mar 7, 2025
@MarkEWaite
Copy link
Contributor

@olivergondza can you approve this so that the adoption process can proceed without waiting for the two week expiration?

@mawinter69
Copy link
Contributor

The plugin is marked for adoption. Doesn't that mean we can proceed immediately?

@MarkEWaite
Copy link
Contributor

The plugin is marked for adoption. Doesn't that mean we can proceed immediately?

You are right. My mistake. Thanks for catching that.

@alecharp
Copy link
Contributor

alecharp commented Mar 7, 2025

We'll need someone to invite you (@simonelbaz) into jenkinsci organisation and in the developer team for the plugin.

@basil
Copy link
Contributor

basil commented Mar 10, 2025

I have invited @simonelbaz to the jenkinsci GitHub organization and the developer team for the OpenStack Cloud plugin. @simonelbaz should be receiving an email shortly and can also visit https://github.com/jenkinsci to accept the invitation.

@alecharp Can you continue processing the hosting request once the invitation is accepted?

@simonelbaz
Copy link
Contributor Author

I have invited @simonelbaz to the jenkinsci GitHub organization and the developer team for the OpenStack Cloud plugin. @simonelbaz should be receiving an email shortly and can also visit https://github.com/jenkinsci to accept the invitation.

@alecharp Can you continue processing the hosting request once the invitation is accepted?

@basil , I accepted the invitation to jenkinsci Github organization. Thanks

@alecharp
Copy link
Contributor

alecharp commented Mar 10, 2025 via email

Copy link
Contributor

@alecharp alecharp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Welcome @simonelbaz !

@alecharp alecharp merged commit f3925c6 into jenkins-infra:master Mar 11, 2025
3 checks passed
@simonelbaz
Copy link
Contributor Author

Welcome @simonelbaz !

Thanks @alecharp :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants