# Issue with setting up automated plugin release

**URL:** <https://community.jenkins.io/t/issue-with-setting-up-automated-plugin-release/6908>\
**Category:** Ask a question\
**Created:** [April 18, 2023, 3:38pm UTC](https://community.jenkins.io/t/issue-with-setting-up-automated-plugin-release/6908 "2023-04-18T15:38:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![accelq](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/accelq/32/3693_2.png) [@accelq](https://community.jenkins.io/u/accelq)\
**Post date:** [April 18, 2023, 3:38pm UTC](https://community.jenkins.io/t/issue-with-setting-up-automated-plugin-release/6908/1 "2023-04-18T15:38:49Z")

</div>

Hi I’m trying to setup my plugin for automated release. Following this article: [Setting up automated plugin release](https://www.jenkins.io/doc/developer/publishing/releasing-cd/) few things that I dont understand.

1. [Here](https://www.jenkins.io/doc/developer/plugin-development/incrementals/) I don’t understand what does this line even means? I ran `mvn incrementals:incrementalify` on my plugin repo. Now?  

2. I see this section in my plugin is still empty. Although it says wait until you see.

---

<div class="post-metadata">

**Author:** ![halkeye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/halkeye/32/8_2.png) [@halkeye](https://community.jenkins.io/u/halkeye)\
**Post date:** [April 18, 2023, 7:27pm UTC](https://community.jenkins.io/t/issue-with-setting-up-automated-plugin-release/6908/2 "2023-04-18T19:27:58Z")

</div>

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](https://github.com/jenkins-infra/repository-permissions-updater) 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.

---

<div class="post-metadata">

**Author:** ![accelq](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/accelq/32/3693_2.png) [@accelq](https://community.jenkins.io/u/accelq)\
**Post date:** [April 19, 2023, 11:17am UTC](https://community.jenkins.io/t/issue-with-setting-up-automated-plugin-release/6908/3 "2023-04-19T11:17:46Z")

</div>

Here is the LINK to PR, its merged.

> <https://github.com/jenkins-infra/repository-permissions-updater/pull/3257>
>
> \# 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**

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/6/663a7d76cee66bf07222e92d8a8137289d26e3c6.png)

---

<div class="post-metadata">

**Author:** ![halkeye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/halkeye/32/8_2.png) [@halkeye](https://community.jenkins.io/u/halkeye)\
**Post date:** [April 19, 2023, 4:15pm UTC](https://community.jenkins.io/t/issue-with-setting-up-automated-plugin-release/6908/4 "2023-04-19T16:15:11Z")

</div>

> [@accelq](#):
>
> Here is the LINK to PR, its merged.

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.

---

<div class="post-metadata">

**Author:** ![accelq](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/accelq/32/3693_2.png) [@accelq](https://community.jenkins.io/u/accelq)\
**Post date:** [May 16, 2023, 10:55am UTC](https://community.jenkins.io/t/issue-with-setting-up-automated-plugin-release/6908/5 "2023-05-16T10:55:56Z")

</div>

Hi [Request to add ACCELQ plugin to auto upload by accelq · Pull Request #3257 · jenkins-infra/repository-permissions-updater · GitHub](https://github.com/jenkins-infra/repository-permissions-updater/pull/3257#issuecomment-1515740824)  
Can someone please let me know if this PR can be merged or not, been waiting for a couple of days now.