Repository navigation
fix(ci): retry transient FTP deploy failures - #21
Merged
Merged
Conversation
This branch was successfully deployed
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.
Summary\n\n- Keep FTP Deploy Action v4.3.6 so missing-directory cleanup remains idempotent.\n- Retry each of the three sequential FTP sync steps up to three times with a 15-second delay, covering transient control-socket timeouts observed on hosted runners.\n- Preserve the existing split upload scopes and sync-state files; no clean-slate deletion.\n\n## Validation\n\n-
▲ Next.js 15.3.0
Creating an optimized production build ...
✓ Compiled successfully in 0ms
Linting and checking validity of types ...
Collecting page data ...
Generating static pages (0/17) ...
Generating static pages (4/17)
Generating static pages (8/17)
Generating static pages (12/17)
✓ Generating static pages (17/17)
Finalizing page optimization ...
Collecting build traces ...
Exporting (0/3) ...
✓ Exporting (3/3)
Route (app) Size First Load JS
┌ ○ / 140 B 113 kB
├ ○ /_not-found 978 B 102 kB
├ ○ /about 5.96 kB 116 kB
├ ○ /apps/consulta-endereco/privacidade 159 B 101 kB
├ ○ /apps/lapscounter/privacidade 159 B 101 kB
├ ○ /apps/validar-gerar-documentos/privacidade 159 B 101 kB
├ ○ /apps/velocimetro-alerta/privacidade 159 B 101 kB
├ ○ /articles 5.13 kB 115 kB
├ ○ /blog 4.33 kB 114 kB
├ ○ /projects 4.16 kB 114 kB
├ ○ /robots.txt 159 B 101 kB
├ ○ /services 140 B 113 kB
├ ○ /sitemap.xml 159 B 101 kB
└ ○ /thanks 173 B 105 kB
├ chunks/4bd1b696-28f2c80879e78373.js 53.2 kB
├ chunks/684-d4f4d53e91ccefd9.js 46.1 kB
└ other shared chunks (total) 1.91 kB
○ (Static) prerendered as static content\n- Workflow YAML parsed and verified all three retry configurations and nested FTP credentials.\n-