Common problems with Events
The messages below appear at the top of the Events tab of a component. GitLab stands for the tool
named in the message: GitHub, Argo CD or SonarQube read the same way.
At the top of the Events tab
| What you see | What to do |
|---|---|
| No Events tab on the component | Turn on Events in Administration › Plugins: see Turn on Events. Check that the catalog-info.yaml of the component carries the annotation of a tool, for example gitlab.com/project-slug. |
The GitLab webhook is not set up: nothing from GitLab reaches this journal. and a link Open the webhooks | Click Open the webhooks, then set the secret on the GitLab card: see Let GitLab send its events. |
The GitHub webhook is not set up: nothing from GitHub reaches this journal. Ask your Astrolabe administrator to set it up. | You are not an administrator: ask yours to set up the GitHub webhook. |
Nothing received from GitLab for this component yet: check that GitLab sends its webhook for this component. | The secret is set, but GitLab has sent nothing for this component. In the GitLab project named by the annotation gitlab.com/project-slug, add the webhook with the address and secret of the GitLab card. |
Nothing received from GitLab for this component since October 30: check that GitLab sends its webhook for this component. | GitLab sends events for other components, not for this one. Add the webhook to this component's project, and check that its annotation names that project exactly, for example acme/shop-app. |
GitLab sends events but no push nor tag: tick pushes and tags in its webhook. | In the webhook of the GitLab project, tick Push events and Tag push events (on GitHub: Pushes and Branch or tag creation). |
GitLab has no webhook: its API is read every 5 min. | Wait 5 minutes, then open the tab again. For the events to arrive right away, set up the webhook: see Let GitLab send its events. |
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). | Create a new GitLab token and replace it in Administration › Company connections › GitLab: see Create a GitLab token. |
Nothing has happened on this component yet. A tool with a webhook shows here from its first webhook received; a tool read every 5 min also brings its last 7 days. | No event has arrived yet. Push a commit to the repository, then open the tab again. |
On a line of the journal
| What you see | What to do |
|---|---|
| A push without a ↳ triggered by the release … line | The commit message does not name the package and its version. Add the line Triggered-By: shop-lib@1.4.2 at the end of the message: see See which release triggered a push. |
↳ triggered by the release 1.4.2 of shop-lib, with shop-lib written but not a link | Declare the component in spec.dependsOn of this component's catalog-info.yaml, for example component:default/shop-lib, and turn on Tech stack in Administration › Plugins. |
Still stuck?
Write to support@forgeit.fr with the name of the component.