Skip to content

Conversation

@rantoniuk
Copy link
Contributor

@rantoniuk rantoniuk commented May 29, 2025

jenkinsci/jira-plugin#468

Link to GitHub repository

https://github.com/jenkinsci/jira-plugin

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

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.

@timja
Copy link
Member

timja commented Nov 21, 2025

There a reason this is still in draft?

@rantoniuk
Copy link
Contributor Author

Yes, haven't decided yet on this.

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.

2 participants