Skip to content

enable cd and update developers #4094

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

guvenkaranfil
Copy link

@guvenkaranfil guvenkaranfil commented Sep 17, 2024

Link to GitHub repository

https://github.com/jenkinsci/appcircle-enterprise-store-plugin
https://github.com/jenkinsci/appcircle-testing-distribution-plugin

When modifying release permission

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

  • @guvenkaranfil
  • @appcircleio

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)
- [x] 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](https://accounts.jenkins.io/).
- [x] All users added have logged in to [Artifactory](https://repo.jenkins-ci.org/) and [Jira](https://issues.jenkins.io/) once.
- [ ] I have mentioned an [existing team member](https://github.com/orgs/jenkinsci/teams) 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.

@guvenkaranfil guvenkaranfil requested a review from a team as a code owner September 17, 2024 09:41
@alecharp alecharp added the needs initial login The users need to log in to Jira and/or Artifactory label Oct 28, 2024
@alecharp
Copy link
Contributor

@guvenkaranfil are you still interested to be able to release those two plugins? If so, please log in Jira with the account appcircleio

Based on #3968, you were the person behind the hosting request for both plugin. So change the account appcircle to appcircleio is expected, correct?

@alecharp
Copy link
Contributor

@guvenkaranfil are you still looking to get this done? Can you please address my previous comment? Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs initial login The users need to log in to Jira and/or Artifactory
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants