Repository navigation
FW-1709: Reduce scheduled Factory tracking runs - #35
Closed
daveosterjr wants to merge 1 commit into
Closed
daveosterjr wants to merge 1 commit into
daveosterjr wants to merge 1 commit into
Conversation
Contributor
|
Dave Oster removed this change from the Factory Work board and closed this pull request. |
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.
Factory status recovery was scheduled every ten minutes even when no source or deployment changed. Run recovery once daily while retaining the existing event reports, manual dispatch, trusted identities and deployment checks.
Tracked in FW-1709. This changes reporting frequency only; it does not deploy an application or change a production release gate.
Validation: parsed the YAML and compared its full structure with the original; only the recovery cron changes. The shared Factory synchronizer regression fails before the repair and passes afterward. Repository CI remains required.
Prepared for the repository owner; no merge or release has been performed.