How to release plugin manually?

Community
1

Hi,

I changed pom.xml - incremented version of our SDK, but release plugin didn’t started yet.

How to run release manually? What I should do for next time automatically triggering release by pom.xml changes?
Thanks !!!

2025: The Year in Review
2

Hi,

which plugin are you referring to?

If you have setup CD on your plugin, you most probably have not set it not to be exclusive. By default, the only way to release a plugin when CD is enabled is through CD.

If you don’t have CD on your plugin, then I usually do mvn release:{prepare,perform} -DreleaseVersion=<THE NEW VERSION I WANT> -B or don’t use the -DreleaseVersion= parameter if the version in the POM is the one you want to release.

If you have CD enabled, and the release haven’t kick in yet, it’s most probably because you haven’t use a label on the pull request your merged that is deemed important enough for the release to start. See jenkins-maven-cd-action/action.yaml at 6d01e3d3f0d952c7ed2fa88df031de46426299c6 · jenkins-infra/jenkins-maven-cd-action · GitHub. If you didn’t, put a label on the pull request you want to release and then trigger the action on GitHub manually. That should do it.

If you haven’t used a pull request, then that’s your answer. In that case, open a pull request with nothing, set a label and merge it. That will not be great for the release note but it’s a quick fix.

3

Thanks Adrien.
This is my plugin: GitHub - jenkinsci/akeyless-plugin: Jenkins native plugin
Can you please look on configuration and tell me how to run release explicitly? The version of plugin generated automatically

Thanks

4

Based on https://github.com/jenkins-infra/repository-permissions-updater/blob/d141edff833941cec9f981695907d78c37f9c348/permissions/plugin-akeyless.yml, cd is not setup on your plugin.
You can run the maven command I provided.

5

Or open a PR in GitHub - jenkins-infra/repository-permissions-updater: Artifactory permissions synchronization tool and data set to enable CD for your plugin. It looks as everything is already in place.

6

I tried to run command like you suggested but got an exception:
akeyless-plugin git:(main) ✗ mvn release:prepare -DreleaseVersion=57.v3f8ea_5dc110e

NFO] [WARNING] Failed to build parent project for io.jenkins.plugins:akeyless:hpi:999999-SNAPSHOT
[INFO] [INFO]
[INFO] [INFO] --------------------< io.jenkins.plugins:akeyless >---------------------
[INFO] [INFO] Building Akeyless Plugin 999999-SNAPSHOT
[INFO] [INFO] from pom.xml
[INFO] [INFO] --------------------------------[ hpi ]---------------------------------
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] BUILD FAILURE
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Total time: 0.753 s
[INFO] [INFO] Finished at: 2025-09-29T13:46:15+03:00
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [ERROR] Unknown lifecycle phase “not-set-up-for-MRP”. You must specify a valid lifecycle phase or a goal in the format : or :[:]:. Available lifecycle phases are: pre-clean, clean, post-clean, validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-site, site, post-site, site-deploy. → [Help 1]
[INFO] [ERROR]
[INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[INFO] [ERROR]

7

I don’t know where this not-set-up-for-MRP is coming from. I don’t see anything in the plugin pom that would call that. Do you have a company settings.xml on your computer?

Be careful because on the plugin repository I can see that you pushed a commit to prepare the release of akeyless-999999 is doesn’t seem right. I’d revert it.

Please run mvn release:{prepare,perform} -B.

8

When I run your command the following file created (release.properties):

#release configuration
#Mon Sep 29 14:54:30 IDT 2025
projectVersionPolicyId=default
scm.branchCommitComment=@{prefix} prepare branch @{releaseLabel}
pinExternals=false
project.scm.io.jenkins.plugins:akeyless.tag=akeyless-999999
projectVersionPolicyConfig={projectVersionPolicyConfig}</projectVersionPolicyConfig>\n exec.activateProfiles=consume-incrementals,might-produce-incrementals pushChanges=true project.rel.io.jenkins.plugins\:akeyless=999999 project.scm.io.jenkins.plugins\:akeyless.connection=scm\:git\:https\://github.com/{gitHubRepo}
scm.rollbackCommitComment=@{prefix} rollback the release of @{releaseLabel}
remoteTagging=true
scm.commentPrefix=[maven-release-plugin]
releaseStrategyId=default
completedPhase=generate-release-poms
scm.url=scm:git:https://github.com/jenkinsci/akeyless-plugin
scm.developmentCommitComment=@{prefix} prepare for next development iteration
project.scm.io.jenkins.plugins:akeyless.developerConnection=scm:git:https://github.com/{gitHubRepo} exec.additionalArguments= scm.tagNameFormat=@{project.artifactId}-@{project.version} project.scm.io.jenkins.plugins\:akeyless.url=https\://github.com/{gitHubRepo}
project.dev.io.jenkins.plugins:akeyless=1000000-SNAPSHOT
scm.tag=akeyless-999999
completionGoals=incrementals:reincrementalify
exec.snapshotReleasePluginAllowed=false
preparationGoals=not-set-up-for-MRP
scm.releaseCommitComment=@{prefix} prepare release @{releaseLabel}
exec.pomFileName=pom.xml

9

If changelist.format is set, use of maven-release-plugin is unexpected and therefore disabled.

1 Like
10

I don’t have settings.xml file

11

akeyless-plugin/.mvn/maven.config at e90c4ab5a036e734d69583dc33a83c73f51e7522 · jenkinsci/akeyless-plugin · GitHub defines the changelist.format.

12

You should enable CD in the repository-permissions-updater (create a new PR). It does not make sense to run maven-release-plugin when everything (well almost everything;-) is set up for CD.

13

Thanks !!!
I enabled CD and build started but it failed at the end of process with authentication error:

[WARNING] Encountered issue during deployment: Failed to deploy artifacts: Could not transfer artifact io.jenkins.plugins:akeyless:pom:62.vb_05cea_69ed08 from/to maven.jenkins-ci.org (Index of releases/): status code: 401, reason phrase: (401)

Should I get/manage some credentials for push artifact?

14

It can take a few hours after enabling CD until the secrets are available in your repo.
You can check that by going to https://github.com/jenkinsci/akeyless-plugin/settings/secrets/actions When you see MAVEN_TOKEN and MAVEN_USERNAME under Repository Secrets you can run the cd action.

15

I got it now - rerun plugin cd and it finished successfully. But I still don’t see newly created plugin not in Akeyless nor in Jenkins plugin configuration. How I can check it released and when I will see it Jenkins configuration? So when I can tell to customer that he can upgrade plugin?

16

On the plugins page it can take again several hours until it becomes visible.
Inside Jenkins click the refresh button and it might be already there. You can already download the hpi file from Index of public/io/jenkins/plugins/akeyless/62.vb_05cea_69ed08