Wildcard in CI check, DX hangout, improved stacked PRs support

Meet Cruise's DX team, restrict account access, stacked PRs aware queue, and more

Mar 22, 2023

🚀 Dev-Productivity hangout with Cruise
🚀 Restrict account access
🚀 Wildcard support for required checks
🚀 Merging Stacked PRs now supported in all queue modes
🚀 Merge conflict detection improvements
🚀 Parallelism cap for paused queues

“Off the record” Dev-productivity Hangout feat. Cruise engineering

We're hosting another installment of our “off the record” hangout series for companies to share knowledge with each other. This month, Cruise's UCI team (unified CI team) will discuss how they reduced CI time and costs on their monorepo. They've done some interesting work with intelligently managing runs, auto-quarantining bad tests, etc. Come hang out with us!

We usually restrict these to ~20 people so that folks get to know each other better. To reserve a spot, reply to this email or ping Spriha at spriha@aviator.co.

Restrict Account Access

If you are an Aviator account admin

you can restrict new account creations from your company domain so that new team members don’t accidentally create parallel accounts. You can still invite new members in the shared account.
you can also enforce Google SSO or SAML login methods for your org.

Wildcard (*) support for required checks

Now you can use wildcards (*) while specifying required CI checks. Example:

required_checks:     
      - "ci/circleci: check_1"
      - "golang-*"  # matches golang-test, golang-lint, etc.

With this wildcard, Aviator will validate all checks with names matching this expression. This validation requires at least one matching check to be present.

Stacked PRs is supported in all modes

Aviator's MergeQueue is now fully stack-aware, regardless of the merge algorithm your org has chosen. All our merge modes including default mode, parallel mode, fast forward mode and affected targets mode support stacked PRs.

Let us know if you have any feedback as you try out Aviator's stacked PRs.

Merge conflict detection improvements

We have added improvements to our core logic to help developers identify the specific subset of breaking PRs during merge conflicts. This will be reported in the PR’s comments.

Parallelism cap for paused queues

A new config field max_parallel_paused_builds now allows you to cap the number of PRs processed on paused base branches (these PRs continue to be processed to check for build breakages but will not merge until the queue is unpaused). The default value is null, which means that PRs on paused base branches will continue to be processed until the max_parallel_builds cap is hit. You can restrict your repository from processing PRs on any paused base branch by setting max_parallel_paused_builds = 0. See our docs for more info.

Bug fixes and improvements

Automatically remove any trigger labels added to draft PRs.
Fixed bug where pausing repos from the webapp dashboard resulted in inconsistencies.
Added detailed validation errors on account page.
Show GitHub API rate limit usage in dashboard.
Improved performance of DB queries.
Sticky comment improvements
- added link to the dashboard queue position.
- immediately update queue position for skip line PRs.
Affected targets mode
- added support for update endpoint and show targets on the Queue page.
- added functionality to filter by affected targets on the Queue page.

Aviator Updates