accelq
April 18, 2023, 3:38pm
1
Hi I’m trying to setup my plugin for automated release. Following this article: Setting up automated plugin release few things that I dont understand.
Here I don’t understand what does this line even means? I ran mvn incrementals:incrementalify on my plugin repo. Now?
I see this section in my plugin is still empty. Although it says wait until you see.
halkeye
April 18, 2023, 7:27pm
2
I feel like i’ve been through this a bunch.
You need to enable incrementals for your repo to enable non release builds.
Then you need to enable cd in GitHub - jenkins-infra/repository-permissions-updater: Artifactory permissions synchronization tool and data set for your plugin.
Since you didn’t include which plugin, any links, we can’t check state at all.
I’m not sure what the second half of your screenshot to create a PR in jenkins core is about. Nothing about your plugin should involve the jenkins core repo.
accelq
April 19, 2023, 11:17am
3
Here is the LINK to PR, its merged.
jenkins-infra:master ← accelq:master
opened 03:21PM - 18 Apr 23 UTC
# Description
# Submitter checklist for adding or changing permissions
…
<!--
Make sure to implement all relevant entries (see section headers to when they apply) and mark them as checked (by replacing the space between brackets with an "x").
-->
### Always
- [ ] Add link to plugin/component Git repository in description above
### When enabling automated releases (cd: true)
- [ ] Add a link to the pull request, which enables continuous delivery for your plugin or component.
Follow the [documentation](https://www.jenkins.io/doc/developer/publishing/releasing-cd/) to ensure, your pull request is set up properly.
### When adding new uploaders (this includes newly created permissions files)
- [ ] [Make sure to `@`mention an existing maintainer to confirm the permissions request, if applicable](https://github.com/jenkins-infra/repository-permissions-updater/#requesting-permissions)
- [ ] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
- [ ] Make sure to `@`mention the users being added so their GitHub account names are known if they require GitHub merge access (see below).
- [ ] [All newly added users have logged in to Artifactory and Jira at least once](https://github.com/jenkins-infra/repository-permissions-updater/#requesting-permissions)
### Reviewer checklist (not for requesters!)
- [ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an [IRC Bot command](https://jenkins.io/projects/infrastructure/ircbot/#github-repo-management)
- [ ] 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](https://jenkins.io/projects/infrastructure/ircbot/#issue-tracker-management) for it
After this step I’m stuck on this one, waiting on MAVEN_TOKEN and MAVEN_USERNAME appear under Repository secrets
halkeye
April 19, 2023, 4:15pm
4
No its not, its specifically still open. You didn’t do the items on the checklist.
I would recommend reading the checklist, and filling out the things you need to fill out, so the volunteers managing all that can review and merge things easily.
accelq
May 16, 2023, 10:55am
5
