Deprecate CI job implementation of Repository X-Ray

Deprecation Summary

• The initial implementation of Repository X-Ray, using a CI job, is deprecated in GitLab 17.6.
• The replacement is an automated background job, triggered when a new commit is pushed to your project's default branch.
• The CI job implementation will be removed from the product as a supported feature in GitLab 18.0 (May 2025).
• If you are using the CI job implementation, please remove the Repository X-Ray job from your .gitlab-ci.yml file.

Breaking Change?

Yes

Affected Topology

• GitLab.com customers that run CI jobs for Repository X-Ray.
• Self-Managed customers that run CI jobs for Repository X-Ray.

Affected Tier

• Premium
• Ultimate

Deprecation Milestone

17.6

Planned Removal Milestone

18.0

Checklists

Click to expand

Labels

• This issue is labeled deprecation, and with the relevant `~devops::`, `~group::`, and `~Category:` labels. - [ ] This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.

Timeline

Please add links to the relevant merge requests.

• As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule: 14.8, 14.9, 14.10, 15.0 – 14.8 is the third milestone preceding the major release):
  • A deprecation announcement entry has been created so the deprecation will appear in release posts and on the general deprecation page.
  • Documentation has been updated to mark the feature as deprecated.
• On the major milestone:
  • The deprecated item has been removed.
  • If the removal of the deprecated item is a breaking change, the merge request is labeled breaking change.

Mentions

• Your stage's stable counterparts have been @mentioned on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.
  • To see who the stable counterparts are for a product team visit product categories
    • If there is no stable counterpart listed for Sales/CS please mention @timtams
    • If there is no stable counterpart listed for Support please mention @gitlab-com/support/managers
    • If there is no stable counterpart listed for Marketing please mention @cfoster3
• Your GPM or Director has been @mentioned so that they are aware of planned deprecations.