fix: stop cancelling Pages deploys, which blocks the deployment queue - #51
Merged
Conversation
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
1 participant
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.
Tres merges seguidos dejaron la web sirviendo el bundle anterior durante una hora, con cada despliegue muriendo en
deployment_queuedhasta agotar el tiempo límite.Causa:
cancel-in-progress: truecancela la ejecución, pero no el despliegue de Pages que esa ejecución ya había encolado. Ese huérfano bloquea la cola y todos los siguientes esperan a un despliegue que nunca va a completarse. El workflow de referencia de GitHub para Pages lo advierte de forma explícita: "do NOT cancel in-progress runs, as we want to allow these production deployments to complete".Con
falselos despliegues se encolan y se ejecutan en orden en vez de pisarse. Para desatascar la cola una vez ocurre:gh workflow run deploy.yml --ref main.