jenkinsci / jenkinsci/subversion-plugin
[JENKINS-17768] Repository URL with parameter triggers failure of the field checker
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 131
- Forks
- 275
- Avg merge
- 12h 4m
- Merged PRs (30d)
- 6
Description
When I use a parameter in the field Repository URL I get a complain from jenkins :
"/Software/amore_modules/${svn_path}" doesn't exist in the repository. Maybe you meant "/Software/amore_modules/trunk"?
I can save it though and it works as expected. It is only the field checker that returns an error. Maybe the checker could use the default value of the parameter instead of taking them litterally ?
Originally reported by barthelemy, imported from: Repository URL with parameter triggers failure of the field checker
- status: Open
- priority: Major
- component(s): subversion-plugin
- label(s): subversion, svn
- resolution: Unresolved
- votes: 0
- watchers: 2
- imported: 20251212-090250
Raw content of original issue
When I use a parameter in the field Repository URL I get a complain from jenkins : "/Software/amore_modules/${svn_path}" doesn't exist in the repository. Maybe you meant "/Software/amore_modules/trunk"?
I can save it though and it works as expected. It is only the field checker that returns an error. Maybe the checker could use the default value of the parameter instead of taking them litterally ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the subversion-plugin field checker for the Repository URL and reproduce the validation with ${svn_path} set to a default path such as /Software/amore_modules/trunk. Compare checker behavior with the successful saved configuration; done means a parameterized URL no longer produces a false missing-repository error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100