Skip to content

Indicate in GitLab UI and logs when GitLab Jenkins CI service fails to trigger or times out

Problem to solve

Self-managed customers using GitLab Jenkins CI project integration are reporting GitLab intermittently fails to trigger Jenkins CI jobs with no indication of failure found in the UI or logs.

Intended users

Further details

GitLab Omnibus 11.10.8

Jenkins CI service is used to trigger external Jenkins job. No .gitlab-ci.yml.

Jenkins CI integration set to trigger on Merge request events.

Jenkins CI jobs are tagged with stage external in the UI, as expected.

When GitLab fails to trigger the Jenkins job on MR, the job shows "Cancelled" in the GitLab frontend on the Merge request page, but not Success/Failed/Pending, as it usually would.

Proposal

If a solution to Problem to solve does not exist:

  • Clearly indicate if GitLab fails to forward jobs to Jenkins CI, in GitLab logs and UI. If a solution or fix already exist:
  • Update documentation with steps on how to reliably determine (and alert) when GitLab fails to forward job to Jenkins using GitLab Jenkins CI plugin.

Documentation

Update https://docs.gitlab.com/ee/integration/jenkins.html#troubleshooting

What does success look like, and how can we measure that?

Customers can reliably identify if and when GitLab fails to forward a job to Jenkins CI via the project integration.

What is the type of buyer?

Jenkins CI service is Starter/Bronze and up.

Links / references

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by 🤖 GitLab Bot 🤖