Common problems with Jenkins

When you add the integration

What you see	What to do
jenkins.example.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 user or the token is wrong. Check Jenkins user, then create a new token: see Create a Jenkins API token.
No server answers to the name jenkins.example.com. 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.	Check Jenkins instance URL: the address you open in your browser, without https://. If it is right, your Jenkins is not reachable from Astrolabe.

On the Plugins screen

What you see	What to do
Configure the Jenkins integration first instead of a switch on the Jenkins card	Add the Jenkins integration. The switch appears once it is added.

On the component page

What you see	What to do
No Jenkins tab	Add the jenkins.io/job-full-name annotation to the component, and turn on Enable Jenkins in Administration › Plugins.
No records to display in the Jenkins tab	Check the annotation: the full name of the job must be the path of the job in Jenkins, for example shop/shop-api. If it starts with a prefix, as in prod:shop-api, prod must be the Jenkins instance key of one of your integrations, or remove prod: to read from the default Jenkins.
No records to display, and the annotation is right	The token may have expired or been revoked. In Administration › Company connections, on the Jenkins card click Manage, then Edit Token, and click Test connection. If it says the credentials are refused, replace the token.
The Latest master build card on Overview says Jenkins has no build for the branch "master" of this component's job. The card looks for that branch: check the job name in the jenkins.io/job-full-name annotation, and that the job builds a "master" branch.	The card reads the branch master of your job. Check the job name in the annotation, and use a job that builds a master branch.
The same card says Jenkins did not answer for the branch "master" (HTTP 500).	Same check, then the Jenkins connection in Administration › Company connections › Jenkins. The words in brackets say what Jenkins answered (no answer or HTTP and a number).
The same card says Jenkins did not answer (no answer).	Check the Jenkins connection in Administration › Company connections › Jenkins.

On My Dashboards

What you see	What to do
Nothing here yet and No build to show: no component of the catalog has a jenkins.io/job-full-name annotation, or its job has no build yet. on a Jenkins card	The card lists the components of the catalog. Check that one of them has the jenkins.io/job-full-name annotation: see Show the Jenkins tab on a component.
Jenkins refused the token.	The token of the integration expired or was revoked. Click Open the Jenkins integration, then on the token click Edit Token, Replace, paste the new token and click Test connection, then Save. To create a token, see Create a Jenkins API token.
Jenkins refuses the connection.	Astrolabe cannot reach Jenkins. Click Open the Jenkins integration and check Jenkins instance URL: the host and the port, without https://. Check that Jenkins is running.
Jenkins does not know what is asked.	Jenkins knows none of the jobs written in your components. Check each name against the path of the job in Jenkins, for example shop/shop-api for the job shop-api in the folder shop.
The builds of one component are missing, the others show	The annotation of that component names a job Jenkins does not know. Check the name, as above.
The Stages column shows -	The job is not a pipeline, so it has no stages. The build is shown with its status and its duration.

Not verified on an instance yet: the three messages of the Latest master build card, no Jenkins is connected to the test instance.

Still stuck?

Write to support@forgeit.fr with the name of the component and its Jenkins job.