Common problems with GitLab
When you add the integration
| What you see | What to do |
|---|---|
Under the GitLab token field: GitLab token is required. | The field is empty; nothing was sent to GitLab. Paste the token. |
gitlab.com refused the credentials (401). Check the token, and that it has not expired. Fix the field above, or save anyway if the source is only unreachable for now. | The token is wrong, revoked or expired. Paste the token alone (it starts with glpat-), or create a new one. |
No server answers to the name <host>. Check its spelling against the address you open in your browser. If it is right, Astrolabe cannot see this server: tell your company's Astrolabe administrator. Fix the field above, or save anyway if the source is only unreachable for now. | Copy the domain name from the address bar of your GitLab, without https:// nor path. If it is right, the server is not reachable from Astrolabe. |
On the component page
| What you see | What to do |
|---|---|
| No GitLab tab | Add the gitlab.com/project-slug annotation (Show the GitLab tab), and check that GitLab is on in Administration › Plugins. |
In the tab or the GitLab releases card: The project <namespace>/<project> cannot be reached with your GitLab token: check the gitlab.com/project-slug annotation, or the token access. | No project has that path, or the token's account cannot see it. Compare the annotation with the project's address on GitLab, then check that the token's account is a member of the project. |
On your dashboard
| What you see | What to do |
|---|---|
| The gitlab source is missing from Add a card | The GitLab integration is not configured. Add it. |
Your GitLab account is not connected. | Click Connect my GitLab account in the card. See Add the GitLab cards to your dashboard. |
GitLab refused the token. The token may have expired or been revoked: replace it in Administration › Company connections › GitLab (or in My account › My accounts if it is your own). | The cards read with your own token, so it is yours that GitLab refuses: revoked, expired, or without the rights. In My Account › My accounts, click Configure on the GitLab card, click Replace next to Token, paste a new token, click Save. |
Nothing here yet and No open merge request in the GitLab projects named by the components of the catalog (gitlab.com/project-slug annotation) that your token can read. | No merge request is open in a project of the catalog that your token reads. If you expected one, check that the component of the project has the gitlab.com/project-slug annotation (Show the GitLab tab) and that your token's account can read the project. |
List cut: too many items to read, only the most recent are shown. above the table of a GitLab card | GitLab holds more than the card can read: the rows shown are the most recent ones. |
Nothing here yet and No pipeline failed or ran lately in the GitLab projects that your token reads and that a component of the catalog names (gitlab.com/project-slug annotation). | Add the gitlab.com/project-slug annotation to the component of the project (Show the GitLab tab), and check that your token's account is a member of the project. |
Nothing here yet and No release published in the GitLab projects named by the components of the catalog (gitlab.com/project-slug annotation) that your token can read. | Add the gitlab.com/project-slug annotation to the component of the project, and check that your token's account can read the project. |
No pending to-do on GitLab and GitLab lists no pending to-do for your account: no review requested, assignment, mention or broken build. | Nothing to fix: the card fills as soon as GitLab has a to-do for you. |
Test Connection in Connect my GitLab account says gitlab.com refused your token (401). Check it, and that it has not expired. | Your token is wrong, revoked or expired. Paste a valid token of your own GitLab account. |
| In My Account › My accounts, the GitLab card says Token refused | Same as above: click Configure, then Replace. |
Notifications
| What you see | What to do |
|---|---|
| No GitLab section in My Account › Notifications | GitLab is not connected: ask your Astrolabe administrator to add the GitLab integration. |
| A failed pipeline does not ring the bell | Check that When a pipeline fails is on in My Account › Notifications, and ask your administrator whether the GitLab webhook is set up (see Get GitLab notifications). |
When the tab says a module is missing
| What you see | What to do |
|---|---|
Astrolabe does not offer this GitLab feature on this instance. and A module is missing from this Astrolabe installation. Tell your Astrolabe administrator. | The integration may be connected and the plugin on, but this installation of Astrolabe lacks the module that serves GitLab. Tell your Astrolabe administrator. Nothing to change on the component. |
Not verified on an instance yet: this message needs an installation that lacks the module.
Still stuck?
Write to support@forgeit.fr with the name of the component and its GitLab project.