jenkinsci / jenkinsci/subversion-plugin

[JENKINS-44297] Allow constructing "custom repo browser url" entries.

Open
#1,419 0 comments 0 reactions 0 assignees View on GitHub
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

Scenario: we're using Upsource both as a code review tool and as a repository browser. Yet it's not listed as a supported repo browser, and we cannot make Jenkins point to specific revisions even knowing their numbers and the url syntax.

It would be nice to allow constructing urls pointing to a specific revision - using meta-elements like $baseurl, $hostname, $projectname/$reponame, $revisionnumber ; maybe also credentials - or whatever other needed stuff. 

Thus, my Upsource url could be constructed from bricks like:

https://$hostname:9443/$reponame/revision/$branchname-$revisionnumber

or 

$baseurl/$reponame/revision/$branchname-$revisionnumber

or just putting everything but the revisionnumber explicitly:

https://my.ho.st.na.me:9443/myrepo/revision/mybranch-$revisionnumber

That could be easily tuned to match probably any repobrowser, and avoid the "jenkins does not support my favorite repobrowser flavor" complaints.

---
Originally reported by vicd, imported from: Allow constructing "custom repo browser url" entries.


  • status: Open
  • priority: Minor
  • component(s): subversion-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 20251212-090250

Raw content of original issue

Scenario: we're using Upsource both as a code review tool and as a repository browser. Yet it's not listed as a supported repo browser, and we cannot make Jenkins point to specific revisions even knowing their numbers and the url syntax.

It would be nice to allow constructing urls pointing to a specific revision - using meta-elements like $baseurl, $hostname, $projectname/$reponame, $revisionnumber ; maybe also credentials - or whatever other needed stuff. 

Thus, my Upsource url could be constructed from bricks like:
https://$hostname:9443/$reponame/revision/$branchname-$revisionnumber
or 
$baseurl/$reponame/revision/$branchname-$revisionnumber
or just putting everything but the revisionnumber explicitly:
https://my.ho.st.na.me:9443/myrepo/revision/mybranch-$revisionnumber

That could be easily tuned to match probably any repobrowser, and avoid the "jenkins does not support my favorite repobrowser flavor" complaints.

  • environment: Jenkins ver. 2.45

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.