jenkinsci / jenkinsci/subversion-plugin
[JENKINS-31352] "List Subversion Tag Parameter" configuration for multi-project repository layout
- Dominant language
- Java
- Stars
- 131
- Forks
- 275
- Avg merge
- 12h 4m
- Merged PRs (30d)
- 6
Description
Given a standard trunk/branches/tags repo layout, suppose you have multiple subprojects, for example:
_http://myserver:myport/svn/rmyrepo/tags/1.0.0/projectA_
_http://myserver:myport/svn/rmyrepo/tags/1.0.0/projectB_
_http://myserver:myport/svn/rmyrepo/tags/1.0.1/projectA_
_http://myserver:myport/svn/rmyrepo/tags/1.0.2/projectA_
Now suppose you have a job for building a specific tag of projectB. "List Subversion Tag" parameter, if configured with "http://myserver:myport/svn/rmyrepo/tags_" as _Repository URL, will show the complete set of tags (1.0.0, 1.0.1, 1.0.2).
No problems if few tags are present, but consider when the repo has tens or hundrends of tags: it's useless and error-prone to show all the tags. Better to show only the tags related to the project to be built.
I propose to improve the configuration options of the "List Subversion Tag" parameter, to let the user configure exactly which tags to include in the list.
Perhaps using a regular expression?
---
Originally reported by vernyquartara, imported from: "List Subversion Tag Parameter" configuration for multi-project repository layout
Raw content of original issue
Given a standard trunk/branches/tags repo layout, suppose you have multiple subprojects, for example:
_http://myserver:myport/svn/rmyrepo/tags/1.0.0/projectA_
_http://myserver:myport/svn/rmyrepo/tags/1.0.0/projectB_
_http://myserver:myport/svn/rmyrepo/tags/1.0.1/projectA_
_http://myserver:myport/svn/rmyrepo/tags/1.0.2/projectA_Now suppose you have a job for building a specific tag of projectB. "List Subversion Tag" parameter, if configured with "http://myserver:myport/svn/rmyrepo/tags_" as _Repository URL, will show the complete set of tags (1.0.0, 1.0.1, 1.0.2).
No problems if few tags are present, but consider when the repo has tens or hundrends of tags: it's useless and error-prone to show all the tags. Better to show only the tags related to the project to be built.I propose to improve the configuration options of the "List Subversion Tag" parameter, to let the user configure exactly which tags to include in the list.
Perhaps using a regular expression?
Contributor guide
Assessment
This issue has not been assessed yet.