Skip to main content

Introducing Low Run Priority Level to Spacelift!

We love when we can deliver features that many of you have specifically asked for. And today is yet another one of those days. Runs on private worker pools now have three priority levels instead of two. You could always push a run priority up, to make sure it is processed first. Now you can push it down, so it waits behind everything at normal or higher levels.

  • UI: Set priority from a run's page, the flag icon in a worker pool's queue, or the three-dot menu. The queue filters and sorts by priority, and bulk actions set the level on multiple runs at once.

  • CLI: spacectl stack priority <low|normal|high> (spacectl 1.26.0+)

  • API: Set it with the runPrioritySet mutation, read it with priorityPreset on Run.

  • Push policies: Return priority (high, normal, or low) to set a run's starting level. The existing boolean prioritize rule still works and maps to high.

Low-priority runs still queue ahead of drift detection. This feature is available on private worker pools only. As always, take it for a spin, and tell us what you think!

Run prioritization docs · Push policy prioritization docs