...
Preparing service account in TDS GitLab by end users
- Make sure service account has access into proper repositories - use portal to check and correct if needed
- Make sure you have credentials for service account, if not, reset them in portal following steps described in Project Details#ServiceAccount
...
- 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
...
- For example for integrating with Jira choose "api, read_
...
- api, read_
...
- user, read_repository, write_repository"
- Copy generated token for later use
- Verify that account can access desired repositories
...
- Use the token as necessary or send request to TDS team with relevant information:
- service account token
- GitLab URL
- Which interation you would like to achieve, for example - Jira project URLs with KEYs that you need to integrate this GitLab with
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://GitLabgitlab.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://GitLabgitlab.shared.CUSTOMERX.tds.tieto.com/admin/users/XXX
- Click "Impersonate"
- Then go to Personal Access Tokens page https://GitLabgitlab.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 Select desired validity or or remove the date to make it never expire - depending on project needs and your security rules and procedures
- Select reasonable scopes
- For example for integrating with Jira choose
- "api, read_
- api, read_
- user, read_repository, write_repository"
- Copy generated token for later use
- Verify that account can access desired repositories
- 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 "MyPortalProject - srv123abc - MyPortalProject"
- Click Update
Generic Git repositories integration
...
- Go to you GitLab project settings, URL shall be like https://GitLabgitlab.shared.CUSTOMERX.tds.tieto.com/PORTAL-PROJECT-NAME/GitLab-PROJECT-NAME/-/services/jira/edit
- Enable it (Active ~ true)
- Select triggers and actions feasible for you
- Enter Jira Web URL, for example https://jira.shared.CUSTOMERX.tds.tieto.com
- Leave "Jira API URL" empty as TDS provides REST api on standard endpoints. If you have some different NON TDS Jira, you might need to specify this REST API URL.
- Username or Email - recommended is username of your project dedicated service account, which is described in Project Details#ServiceAccount
- Password or API token - recommended is token of your project dedicated service account, which is described in Project Details#ServiceAccount
More details can be found in GitLab documentation https://GitLabgitlab.shared.pub.tds.tieto.com/help/user/project/integrations/jiraJira
GitHub Enterprise integration with Jira
After it is integrated, just give it some time, commits become to be visible with delay especially if many repositories is configured.