🚀 Cancel stale CI pipelines

[kikoveiga]

Motivation

Stale branch pipelines keep consuming CI capacity after newer commits supersede them.

Changes

• Default CI jobs to interruptible: true.
• Auto-cancel interruptible jobs on non-main branches when a new commit is pushed.
• Preserve existing pipelines on main and tags.
• Keep manual container-image builds non-interruptible.

This follows the configuration already used in dd-sdk-android and DataDog/shopist-android#257.

Test instructions

• yarn prettier --check .gitlab-ci.yml
• Parsed .gitlab-ci.yml with Ruby YAML.
• Asserted the workflow cancellation modes and container-image exception from the parsed configuration.

Checklist

• Tested locally (CI configuration validation; playground is not applicable).
• Added unit tests for this change. Not applicable: CI-only configuration.
• Added e2e/integration tests for this change. Not applicable: CI-only configuration.
• Updated related documentation. Not applicable: behavior is documented inline in .gitlab-ci.yml.
• Agentic code review findings addressed or explicitly dismissed.

[cursor]

PR Review — Score: 4.9 / 5

This is a focused CI hygiene change: default jobs are interruptible, superseded branch pipelines auto-cancel, and main/tags plus the manual build-container-image job are explicitly protected. The workflow rules are correctly scoped and align with the established dd-sdk-android pattern. I would approve.

Why 4.9: Minimal, well-commented diff with the right exception for long-running manual Docker builds, and the author validated YAML structure locally. No SDK or customer-facing impact.

Why not 5: CI-only configuration changes inherently lack in-repo regression tests beyond static parsing; operational correctness depends on GitLab runtime behavior. Several dd-gitlab/* jobs were still running when this review was posted (not a merge blocker).

  

_{Sent by Cursor Automation: electron-sdk reviews}