Page Comparison

...

Sealights attempts to create links back to the customers SCM based  on the repo URL and the type and version of the SCM the customer uses.
In some cases this cannot be created properly as the repo URL is different to the actual URL used when browsing to the files through a browser.

1. Wrong SCM type is sent to Sealights

2. Wrong bitbucket on premise version - As Bitbucket has changed their link format between versions, if the wrong version is provided to Sealights the link can be incorrect

3. Different DNS and port - The DNS and port used by the CI could be different to the one used when browsing to the files through a browser. This mainly happens when connecting in the CI through ssh rather than https

4. CI uses a local repo and in turn sets the repo URL to be a local or temp path rather than the real repo

Solution

Sealights provides the ability to set what the correct values should be with 3 parameters. See various agent documentation on means to doing so

...

If not identified automatically you should provide the following based on your SCM:

SCM version

Should be set for any On-Premise SCM type.
If using a cloud SCM and the repo URL is not sent correctly, this should be set to "cloud"

...