Bitbucket Server

The information below applies to repositories on Bitbucket Server.  It explains how to grant Hackolade Studio access to your Bitbucket Server account, which is a pre-requisite for using the features "submit for review" and "review change requests".

 

Note: that access to the Bitbucket Server is not sufficient by itself.  The user also need proper access rights the repositories, according to the 4 levels of Bitbucket Server permissions.

 

Personal HTTP access tokens

Important note: in later releases of Bitbucket Server, it is now possible to issue Project tokens.  We discourage the use of Project tokens in the context of Hackolade Studio.  With Project tokens, Bitbucket Server automatically assigns a new internal username to users, resulting in identification issues in terms of Git history and Pull Requests, as well as other anomalies.  Personal HTTP tokens should be used instead.

 

In the repository connection manager, click on the "generate" link located to the right of the input field for the personal access token. You can find more information on how to generate a personal access token in the Bitbucket Server documentation.

 

Depending on the version of Bitbucket Server, you may also be prompted for your username, so the application can assemble the right link in the "generate" button:

 

 

.

Clicking on the "generate" link brings you to the Bitbucket Server form.  Note that, in terms of permissions, Hackolade Studio requires at minimum the "repository write" permission in order to be able to perform Pull Requests actions.

 

If you don't have sufficient rights to issue tokens, you may have to request one from your administrator.  

 

To re-issue an expired token, proceed like creating a new one, then:

• navigate to your list of personal access tokens on Bitbucket Server;
• click on the Create Token button in order to create a new token;
• edit the connection in Hackolade, as described above, and copy-paste the new token from Bitbucket Server.

 

If you don't have a valid Personal Token, you may get the error message below, indicating that your token has passed its expiration date, or that it does not have the right permissions enabled.

 

If you see this message, please follow the instructions above.

 

Username and Password

Alternatively, you may use your account username and password, but it is typically discouraged for security reasons. With a token, if an external system is compromised, you simply revoke the token instead of changing password, and consequently changing it in all scripts and integrations. It is recommended you only map one token per integration, then If the integrated system is compromised, you can remove that token and not affect any of the other integrations.

 

In the repository connection manager, select Connect with Username and Password and enter your credentials.