BuildOn changes specific to Atlassian Bitbucket

BuildOn SCM page for Bitbucket requires only the repo url. Access token is not required.
The SSH key must be configured inside Bitbucket as mentioned in section “Bitbucket prerequisites with BuildOn”

Bitbucket prerequisites for BuildOn

Recommended BitBucket version: 5.7.0 or above.
The SSH key must be generated on the BuildOn Framework Server and the respective public key (id_rsa.pub) content must be configured at service account level within Bitbucket.

Refer the following link to set up ssh key

https://confluence.atlassian.com/bitbucket/set-up-an-ssh-key-728138079.html

Known Issues:

Jenkins Pipeline check-in from BuildOn Web UI, will be committed to Bitbucket in the name of the user configured with the SSH key instead of the actual user logged in to BuildOn Web UI. As a result the build reports for respective Jenkins Pipeline check-in will bear the SSH username. Web-hook in "Preference" page will not take effect when committed using "Check In" option from UI.

Reason - BuildOn UI uses SSH token for cloning/committing repo from Bitbucket.

All other check-ins directly to Bitbucket repository and triggers from BuildOn UI shall not have any issues and will continue to work as usual.

Browser not supported