chore: Increase delay in publish "legacy" podspecs job #2045
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
so it starts 20 minutes after "dependent" job, ensuring that at least some of "dependent" podspecs are available in trunk. Otherwise, "legacy" job will always fail and require manual restart.
mariedm
approved these changes
Sep 11, 2024
ganeshnj
approved these changes
Sep 11, 2024
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.
What does this PR do?
🧰 This PR adds an additional 20-minute delay to the "Publish CP podspecs (legacy)" release job. The extra time ensures that "internal" and "dependent" podspecs, published earlier, are available, reducing the need for manual job restart.
This delay should have been included in PR #1945 but was missed due to an oversight.
How?
The job configuration was updated to include the extended delay.
Review checklist