jenkinsci / jenkinsci/subversion-plugin

[JENKINS-32187] List Subversion tags doesn't populate during release configuration

Open
#1,335 0 comments 0 reactions 0 assignees View on GitHub
component:release-plugin component:subversion-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
131
Forks
275
Avg merge
12h 4m
Merged PRs (30d)
6

Description

If "configure release build" is checked (release plugin) and "List Subversion tags" is added as a release parameter, no tags are listed. If the exact same options are added but as a standard build parameter, the tags are listed. Furthermore, if the options are added as a build parameter in both places, both parameters are displayed but they both list the tags according to the standard build parameter. If the parameter name is changed on one so that they no longer match, the release parameter will no longer list the tags.

The release parameter is not being evaluated. It is being populated when the standard parameter is evaluated.

'Override build parameters' has no effect. It was selected in the attached images for demonstration purposes.

---
Originally reported by naugler, imported from: List Subversion tags doesn't populate during release configuration


  • assignee: recena
  • status: Open
  • priority: Minor
  • component(s): release-plugin, subversion-plugin
  • label(s): release-plugin, subversion, tags
  • resolution: Unresolved
  • votes: 1
  • watchers: 1
  • imported: 20251212-090250

Raw content of original issue

If "configure release build" is checked (release plugin) and "List Subversion tags" is added as a release parameter, no tags are listed. If the exact same options are added but as a standard build parameter, the tags are listed. Furthermore, if the options are added as a build parameter in both places, both parameters are displayed but they both list the tags according to the standard build parameter. If the parameter name is changed on one so that they no longer match, the release parameter will no longer list the tags.

The release parameter is not being evaluated. It is being populated when the standard parameter is evaluated.

'Override build parameters' has no effect. It was selected in the attached images for demonstration purposes.

environment

```
jenkins 1.643

subversion-plugin 2.5.5

release-plugin 2.5.4
```

4 attachments

- [release_and_standard.PNG](https://issues.jenkins.io/secure/attachment/31532/release_and_standard.PNG)
> ![release_and_standard.PNG](https://issues.jenkins.io/secure/attachment/31532/release_and_standard.PNG)
- [release_name_change.PNG](https://issues.jenkins.io/secure/attachment/31531/release_name_change.PNG)
> ![release_name_change.PNG](https://issues.jenkins.io/secure/attachment/31531/release_name_change.PNG)
- [release_notworking.PNG](https://issues.jenkins.io/secure/attachment/31533/release_notworking.PNG)
> ![release_notworking.PNG](https://issues.jenkins.io/secure/attachment/31533/release_notworking.PNG)
- [standard_working.PNG](https://issues.jenkins.io/secure/attachment/31534/standard_working.PNG)
> ![standard_working.PNG](https://issues.jenkins.io/secure/attachment/31534/standard_working.PNG)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.