This repository has been archived by the owner on Mar 18, 2024. It is now read-only.
Enable pools to succeed on deployment errors by default #755
Conversation
This file contains 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
azlam-abdulsalam
changed the title
This was referenced Mar 11, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
There have been multiple feedback from the community, that prepare breaks quite often when there is a missing setting or a dependency cycle,resulting in scratch orgs not being created and the pools not available.
The option is to allow partial scratch orgs, rather than nothing at all. In order to enable this, succeedOnDeploymentErrors will be enabled as the default behaviour