-
Bug
-
Resolution: Fixed
-
Medium
-
2.1.5
This is most obvious when the FishEye repository is a subset of the underlying SCM repository.
Current example
Facts:
Base SVN url | https://studio.atlassian.com/svn/ |
Checkout SVN url | https://studio.atlassian.com/svn/FE/trunk |
FishEye url | https://extranet.atlassian.com/crucible/ |
FishEye base browse url | https://extranet.atlassian.com/crucible/browse/FE/ |
FishEye url for checkout | https://extranet.atlassian.com/crucible/browse/FE/ |
FishEye base changelog url | https://extranet.atlassian.com/crucible/changelog/FE/ |
Bamboo allows the specification of a Web Repository URL and an optional Web Repository Module.
when | Example 1 | |
---|---|---|
WR URL = | https://extranet.atlassian.com/crucible/browse/FE | |
WR Module = | (blank) | |
then | worked? | |
file link | https://extranet.atlassian.com/crucible/browse/FE/FE/trunk/src/java/com/cenqua/crucible/revision/diff/patchDiff/PatchDiff.java?content-type=text/vnd.viewcvs-markup&root= (double repository name, content-type and root= not used) | |
version link | https://extranet.atlassian.com/crucible/browse/FE/FE/trunk/src/java/com/cenqua/crucible/revision/diff/patchDiff/PatchDiff.java?content-type=text/vnd.viewcvs-markup&root=&revision=24474&r=24474#r24474 | |
diff link | https://extranet.atlassian.com/crucible/browse/FE/FE/trunk/src/java/com/cenqua/crucible/revision/diff/patchDiff/PatchDiff.java?content-type=text/vnd.viewcvs-markup&root=&r1=24473&r2=24474 | |
changeset link | https://extranet.atlassian.com/crucible/changelog/FE?cs=24474 |
Immediate bug fixes
- As shown in example 3, when constructing changeset links, Bamboo should put the WR Module (if present) in the path
- If running in "pure fisheye links" mode
- don't add content-type and root query params (unecessary in examples 1, 2 and 3)
- If running in "viewcvs compatible mode"
- Add a rev (in addition to the r and revision) query parameter. (example 4)
Root cause
Bamboo cannot be configured to know that a FishEye repository (or any Web Repository URL) represents a subset of the underlying repository. The examples above don't cover all the possible failure modes because (conveniently) the prefix path "/FE/" coresponds to the name of the repository in the FishEye instance. (Also see BAM-2568)
Possible solutions
- Add a Web Repository Module Prefix parameter, which is the prefix at which the FishEye repository is configured.
- Allow a general regex mechanism for constructing link urls (
BAM-1354) - Add a plugin point for generating SCM links (and for configuring said plugin in the Source Repository plan config page. (related BAM-1602).
- incorporates
-
BAM-1054 Changes in SVN Externals do not generate correct Fisheye links
- Closed
-
BAM-2611 Bamboo doesn't generate correct FIshEye links for Perforce
- Closed
-
BAM-3150 A Build's change file list does not produce the correct links to fisheye in bamboo 2.2 snapshot
- Closed
-
BAM-1602 Bamboo should JIRA style linkformat to integrate better with other webrepositories.
- Gathering Interest
- relates to
-
BAM-2568 FishEye integration should support FishEye instances configured to view a subset of a VCS repository
- Closed
-
BAM-3522 Perforce FishEye linking
- Closed