chore: improve reliability of deploy integration tests#7951
Merged
Conversation
This [mechanism already exists](https://github.com/netlify/cli/blob/b80b98f85929803fc35a08458c9327dc7ef63de0/tests/integration/utils/create-live-test-site.ts#L22-L36) but wasn't being used here, so it was falling back to the first account the user has access to that is returned by the accounts API. The `netlify-integration-testing` account is properly configured to host our various integration test sites, e.g. to avoid being rate limited.
📊 Benchmark resultsComparing with b80b98f
|
dd737b2 to
25ec325
Compare
sarahetter
approved these changes
Feb 18, 2026
eduardoboucas
approved these changes
Feb 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The deploy command integration tests have become extremely unreliable recently. This PR makes them pass reliably.
create integration test sites in testing account
This mechanism already exists but wasn't being used here, so it was falling back to the first account the user has access to that is returned by the accounts API.
Integration tests in CI were often failing lately, and under the hood it appears to be because requests to the test sites we're creating on the fly were being rate limited.
The
netlify-integration-testingaccount is properly configured to host our various integration test sites, e.g. to avoid being rate limited.lower test concurrency
Running multiple entire build + deploy cycles concurrently results in a lot of network requests that may cause resource contention anyway, so lower the default concurrency from 5 to 3.
increase test timeout
The timeout was 90s, which is a pretty low threshold given that 36 of these tests run in each job, multiplied by 4 test matrix variations, multiplied by however many jobs happen to be running. We were even within the test giving a 5 min timeout to the underlying
ntl deploy, but this could never be reached because the test itself stopped after 90s.Bump this up to 5 mins.