-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins ver. 2.45
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.
[JENKINS-44297] Allow constructing "custom repo browser url" entries.
Summary | Original: Allow constructiong "custom repo browser url" entries. | New: Allow constructing "custom repo browser url" entries. |
Description |
Original:
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 |https://%24baseurl:9443/$reponame/revision/$branchname-$revisionnumber]or [$baseurl/$reponame/revision/$branchname-$revisionnumber |https://%24baseurl:9443/$reponame/revision/$branchname-$revisionnumber]or just putting everything but the revisionnumber explicitly: [https://my.ho.st.na.me:9443/myrepo/revision/mybranch-$revisionnumber|https://%24baseurl:9443/$reponame/revision/$branchname-$revisionnumber] That could be easily tuned to match probably any repobrowser, and avoid the "jenkins does not support my favorite repobrowser flavor" complaints. |
New:
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. |
Issue Type | Original: Improvement [ 4 ] | New: New Feature [ 2 ] |