Thanks to visit codestin.com
Credit goes to github.com

Skip to content
This repository was archived by the owner on Mar 18, 2024. It is now read-only.
This repository was archived by the owner on Mar 18, 2024. It is now read-only.

feat: Always use the newest validation scratch org during Validate #1228

Description

@petter-eikeland

Describe the feature enhancement
We are using the thorough mode in our Validate Process. At the start of a typical day the first PRs are fast as only the newest changes are validated. However, throughout the day the PR validation gets slower and slower. This is because the validation org was created at midnight and tests the same functionality that was merged to master and built successfully earlier the same day.

We are Replenishing the Validate Pool at midnight, 10, 12 and 14. If Validate always used the newest scratch org in the pool, it would mitigate some of this slowdown as it would already contain the latest changes from the same day.

Metadata

Metadata

Labels

analysisTo be decided on how to solution/fix

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions