ci: remove the code navigation job

Kai Armstrongrequested to merge
ci/remove-code-navigation-job into main

What does this MR do?

Removes the golang-code-intel CI/CD component include, which provided the code_navigation_golang job.

Why?

The job cannot succeed. scip-go indexes the project fine and scip convert produces dump.lsif, but the artifact is over the ci_max_artifact_size_lsif limit, so the upload is rejected and the job exits 1:

dump.lsif: found 1 matching artifact files and directories
ERROR: Uploading artifacts as "lsif" to coordinator... 413 Request Entity Too Large
FATAL: too large
ERROR: Job failed: exit code 1

It failed in 19 of the last 20 default-branch pipelines (the 20th didn't run the job at all), at 2 to 5 minutes of runner time each. Recent examples:

Pipeline Job
#14163 16528920577
#14160 16527119476
#14149 16525805941
#14137 16521153432

Since the component sets allow_failure: true, this never blocked a pipeline, which is why it has gone unnoticed. It has been burning runner time and showing a permanently red job in the pipeline view.

There's no longer a reason to fix it. Code navigation supersedes LSIF-backed code intelligence for this project. It reads the knowledge graph GitLab Orbit builds from the code and updates on push, so it needs neither an indexer nor a CI/CD job. It reached beta in GitLab 19.0 and was enabled on GitLab.com in 19.4.

How to verify

  • glab ci lint passes with the include removed.
  • Nothing else in the repository references the LSIF artifact or the component: grep -rn "code-intel\|code_navigation\|dump.lsif\|scip" . returns no other hits.
  • GO_VERSION was the component's only input but is still used by several other jobs, so the variable stays.
  • After merge, the next default-branch pipeline should have no code_navigation_golang job.

🤖 Generated with Claude Code

Merge request reports