Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
-
4.7.2
Description
Using Git Plugin 3.0.0 the following Link is generated for Source-File-Changes using BitbucketWeb:
https://myhostedbitbucket/projects/myProject/repos/myRepo/history/package/of/java/class.java
Link leads to 404 - correct would be
https://myhostedbitbucket/projects/myProject/repos/myRepo/browse/package/of/java/class.java
"history" was dedected hardcoded in
https://github.com/jenkinsci/git-plugin/blob/e3b32afe0697ec2825fb86b82417f311874cecc5/src/main/java/hudson/plugins/git/browser/BitbucketWeb.java#L70
Attachments
Issue Links
- relates to
-
JENKINS-67066 Each commit in "Changes" links to "stash" rather than "bitbucketserver"
-
- Closed
-
- links to
It has been a couple of years, so I don't know if this was the original cause of the problem. However, I contacted Atlassian/Bitbucket and was able to confirm that this behavior is related to the "New Source Browser Experience". When I disabled this feature (in the Bitbucket Labs page of my accounts settings), I was able to see the expected commit history of the specific file.
It also appears that this is NOT the desired effect of the New Source Browser Experience. So I am expecting some time in the future, this will be fixed in Bitbucket and we will not need to disable New Source Browser Experience in order for this history link to work.