jenkinsci / jenkinsci/subversion-plugin

[JENKINS-32140] List non-default subversion tags (as parameter) for Repos containing trunk/branches/tags

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

Description

We use an additional svn sub-folder for "personal" development or preparation in addition to the default trunk/branches/tags - structure. In this case, this folder-hierarchy isn't shown in parametrized builds (regardless of the applied filter).

This behaviour is documented in the corresponding help ...


You can also specify the root of a Subversion repository: If this root contains the trunk, branches and tags folders, then the dropdown will display trunk, all the branches and all the tags. If the root does not contain these three folders, then all its subfolders are listed in the dropdown.

Now, I want to request you for a small feature-extension to solve our/this problem, i.e.,



  • Possibility 1: Check-box to choose default-behaviour versus showing all, regardless of existence of trunk/branches/tags

  • Possibility 2: Optional (but simple) "pre-filter" to limit tags-search to 1-n (direct) sub-folders; before filtering by the Tags-filter (with regex) occurs.

  • ... Or any "better" you will find ...

As I've understood your Code (e.g. ListSubversionTagsParameterDefinition.java) possibility 2 seems to be simpler to implement and may speedup list-creationg for non-default structures.

Best regards from Salzburg,

Markus Eisenmann

---
Originally reported by ibiatiroler, imported from: List non-default subversion tags (as parameter) for Repos containing trunk/branches/tags


  • status: Open
  • priority: Major
  • component(s): subversion-plugin
  • resolution: Unresolved
  • votes: 3
  • watchers: 4
  • imported: 20251212-090250

Raw content of original issue

We use an additional svn sub-folder for "personal" development or preparation in addition to the default trunk/branches/tags - structure. In this case, this folder-hierarchy isn't shown in parametrized builds (regardless of the applied filter).

This behaviour is documented in the corresponding help ...


You can also specify the root of a Subversion repository: If this root contains the trunk, branches and tags folders, then the dropdown will display trunk, all the branches and all the tags. If the root does not contain these three folders, then all its subfolders are listed in the dropdown.

Now, I want to request you for a small feature-extension to solve our/this problem, i.e.,



  • Possibility 1: Check-box to choose default-behaviour versus showing all, regardless of existence of trunk/branches/tags

  • Possibility 2: Optional (but simple) "pre-filter" to limit tags-search to 1-n (direct) sub-folders; before filtering by the Tags-filter (with regex) occurs.

  • ... Or any "better" you will find ...

As I've understood your Code (e.g. ListSubversionTagsParameterDefinition.java) possibility 2 seems to be simpler to implement and may speedup list-creationg for non-default structures.

Best regards from Salzburg,
Markus Eisenmann

environment

```
Jenkins 1.642 on Windows Server 2008 (x64),

Subversion plugin Version 2.5.5
```

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.