GitLab

The information below applies to repositories hosted on GitLab (cloud on gitlab.com and self-hosted instances.)  It explains how to grant Hackolade Studio access to your GitLab account, which is a pre-requisite for using the workflow features submit for review and review change requests.

 

Personal Access Tokens

GitLab provides different types of tokens.  One might be tempted to use, for example, a Group access token.  As indicated in the GitLab documentation, "Group access tokens are treated as internal users. If an internal user creates a group access token, that token is able to access all projects that have visibility level set to Internal.", which is most likely undesirable here.  Plus, group tokens do not provide the traceability required for our use case.  To avoid any issues, make sure to create Personal Access Tokens only.

 

In the repository connection manager, you need to provide an access token, which is a complex password that must be generated by GitLab.

 

 

Click on the "generate" link located to the right of the input field to navigate to the personal access token creation screen of GitLab. You need to click on the button "Create personal access token", as all the required fields should be pre-filled automatically. The access token will be available for you to copy at the top of the page.

 

 

Then paste the access token in Hackolade Studio and click the "Connect" button.  Take a look at the GitLab documentation for more information.

 

OAuth

INFO: connecting with OAuth is only possible if you use GitLab cloud and is not supported for self-hosted instances.

 

As an alternative to generating a personal access token, GitLab can also let you grant Hackolade Studio access to your account through OAuth.

 

 

You just need to click on the "Connect" button to get the instructions below in your browser.

 

 

Click on "Authorize", close the browser window/tab and go back to Hackolade Studio: it should now be connected to GitLab.

 

 

Troubleshooting

For issues when Git clone or push fails a GitLab repository, please consult this GitLab article.

 

A possible cause, as provided by the HackoladeGit.log can be "SSL certificate problem: unable to get local issuer certificate".  This is caused by the fact that your organization might be using self-signed certificates (often in the context of dev or test environments -- rarely in prod environments...) and this self-signed certificate is not present in the local certificate storage.  This situation and the solution are well described in this GitLab link.