Fast-track your critical builds with Build Priority! 🚀

Changelog Website
,
1

Hey Bitrise users :waving_hand:

Ever found yourself in a situation where a crucial build gets stuck at the back of a long queue? We know the feeling! When concurrency limits kick in, those vital builds can get delayed, slowing down your team’s momentum. Enter, Build Priority :up_arrow:

Build priority
Build priority3024Ă—1824 391 KB

:package: What’s new?

  • With Build Priority, you can now “fast-track” important builds to the front of the queue, ensuring they get executed first.
  • Assign a number between –100 and 100 (the default is 0) to pipelines, workflows, triggers, or even during the Build Start process.
  • When your project hits concurrency limits, your high-priority builds will run first—ensuring your critical work never gets stuck waiting.

:guide_dog: How It works

Set priorities easily through:

  1. The Priority field for Workflows or Pipelines
  2. The Priority field for triggers
  3. The Priority field for Build Start dialog or via API calls for a quick override.

Check out the docs here.

:eye: Seeing is believing:
You’ll see the priority of queued builds right on their build cards in the build list. Just hover over the priority flag to see the numerical value.

:bullseye: Who benefits?
This feature is perfect for larger DevOps teams that often encounter concurrency limits. If you’re on our Teams, Pro, or Enterprise plans, you’ll see the advantages.

:shortcake: Ready to give it a try?
Update your build configurations and let Build Priority help you run your most critical builds faster. We’re excited to see how this feature makes your CI/CD process smoother and more efficient. Check out the docs here.