jenkinsci / jenkinsci/release-plugin

[JENKINS-22655] Release Plugin 2.4.1 don't seems to work with current Jenkins version 1.555

Open
#111 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component:release-plugin imported-jira-issue priority:major regression resolution:unresolved
Dominant language
Java
Stars
24
Forks
46
PR merge metrics
No merged PRs in 30d

Description

While manually triggering a release build, configured pre- and post release build steps of the Release Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Release+Plugin) seems not to be honoured.

We want to change the versions via maven-versions-plugin before and after a release build, but the respective call of the maven goals cannot be found in console log (and poms aren't changed). Calling the maven goals from the command line works as expected.

Is this plugin version compatible with Jenkins 1.555?


Originally reported by h_stolzenberg, imported from: Release Plugin 2.4.1 don't seems to work with current Jenkins version 1.555
  • assignee: petehayes
  • status: Open
  • priority: Major
  • component(s): release-plugin
  • label(s): compatibility, plugin, release
  • resolution: Unresolved
  • votes: 0
  • watchers: 2
  • imported: 20251223-222157
Raw content of original issue

While manually triggering a release build, configured pre- and post release build steps of the Release Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Release+Plugin) seems not to be honoured.

We want to change the versions via maven-versions-plugin before and after a release build, but the respective call of the maven goals cannot be found in console log (and poms aren't changed). Calling the maven goals from the command line works as expected.

Is this plugin version compatible with Jenkins 1.555?

  • environment: Debian, Jenkins 1.555, Release Plugin 2.4.1, M2 Release Plugin 0.13.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported setup with Debian, Jenkins 1.555, Release Plugin 2.4.1, and M2 Release Plugin 0.13.0, using configured pre- and post-release Maven goals. Inspect the release-plugin handling of those steps and compare the console log and POM changes with command-line behavior; done means both configured goals run during a manual release build.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devops, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.