...
| Note |
|---|
These instructions are made for TDS users. Getting service account into your local Gitlab installations will be similar in principle, however you need to adapt them on your environment. |
Preparing service account in TDS GItlab by end users
- Make sure you have credentials for service account, if not, reset them using portal in portal project detail
- Add service account into proper repositories using portal
- Open inkognito/private window
- Login to Gitlab using service account credentials
- Then go to Personal Access Tokens page https://gitlab.shared.CUSTOMERX.tds.tieto.com/profile/personal_access_tokens
- Fill the name , for example like "jira-integration"
- Leave Expires at EMPTY to keep it unlimited depending on project needs
- Choose "read_user, read_api, read_repository, write_repository"
- Copy generated token for later use
- Verify that account can access desired repositories
Preparing service account in TDS GItlab by TDS support/consultancy team
- Add service account into proper repositories using portal
- Go to Gitlab users list https://gitlab.shared.CUSTOMERX.tds.tieto.com/admin/users
- Search for that service account and open it by clicking username or simply go to user profile using this direct link while replacing XXX with username - https://gitlab.shared.CUSTOMERX.tds.tieto.com/admin/users/XXX
- Click "Impersonate"
- Then go to Personal Access Tokens page https://gitlab.shared.CUSTOMERX.tds.tieto.com/profile/personal_access_tokens
- Fill the name , for example like "jira-integration"
- Leave Expires at EMPTY to keep it unlimited depending on project needs
- Choose "read_user, read_api, read_repository, write_repository"
- Copy generated token for later use
- Verify that account can access desired repositories
- Stop impersonation
Setting Git integration in Jira by administrators
- Then stop impersonation
- Go to https://jira.shared.CUSTOMERX.tds.tieto.com/secure/ViewGitRepositories.jspa
- Click Gitlab in auto-connect options
- Provide Gitlab URL
- Enter access token generated in previous step
- Click Next and check loaded projects/repositories list to see whether accesses are correct and make sure to fix it
- Click Continue
- Untick "Associate with all projects" and choose proper Jira projects to map selected repositories to
- Or enable PAT for users interactions with Gitlab which is even better but can be very confusing and complex for users
- Click Finish
- Find newly created integration
- Click gear next to it and select "Edit integration connection settings"
- Change "Display Name" from Gitlab URL to service account username and something which represents that integration, usually portal project name, for example "srv123abc - MyPortalProject"
- Click Update
Generic Git repositories integration
...
- service account is recommended to be created in remote Git solution
- SSH key, username and password or personal access token must be generated for that service account
- access to proper repositories must be granted to this service account
- Jira admins shall setup integration using provided service account credentials and all required repositories one by one