Canary: schedule `ci.yml` and `publish.yml` ahead of the consumers' Monday builds (PLAN P0 0c)

Abierto
  • ¿Algo no está bien?
#302 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, shell
Área
ci-cd

Línea de trabajo

Read .github/workflows/cache.yml, ci.yml, and publish.yml, then review the gate workflows in #135 and #136 and the deployment concern described here. Map how scheduled runs, preview deployment results, and the shared pages concurrency group interact before changing the schedules and run conditions. Done means scheduled CI and publish runs execute successfully, both previews report deployed as 'true', and the gate's fixture site is not left replaced without a recovery plan.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

infrastructure low-priority

PLAN's P0 item 0c, split out of #138 when that tracker closed. The release gate (#135, #136) tests a candidate before v0 moves, but only when a releaser dispatches it. Between releases, a change outside this repository, such as a deploy service's API, a CLI or the :latest image, reaches the canary's preview and publish paths no sooner than it reaches the consumers.

What the canary, QuantEcon/test-actions-lecture-intro, runs today (checked 2026-11-10):

  • cache.yml runs weekly on Sunday at 03:00 UTC and by hand, a day ahead of the consumers' Monday builds. It is the only canary path with a lead.
  • ci.yml runs on pull_request and workflow_dispatch, with no schedule. Its preview-netlify and preview-cloudflare steps pass no dispatch-alias, so a dispatched run deploys nothing and still goes green.
  • publish.yml runs only on a publish* tag push. It has no workflow_dispatch, and its job-level if: accepts only tag pushes, so a scheduled or dispatched run would skip its only job and never go red.

The change PLAN describes:

  • schedule ci.yml and publish.yml ahead of Monday, as cache.yml is;
  • have ci.yml pass dispatch-alias and fail unless each preview reports deployed as 'true';
  • give publish.yml an if: that accepts a scheduled run.

To settle when this is picked up:

  • publish.yml and the gate's publish-deploy deploy the same GitHub Pages site, in the pages concurrency group. A scheduled publish replaces the gate's fixture site with the canary's, and the next gate run swaps them back.
  • How a failed scheduled run reaches a person. A canary that failed eight weeks running and filed no issue is #83.

PLAN defers this until the gate has replaced the hand-staged legs that these two workflows still carry. v0.18.0 runs the gate and the hand legs side by side once, as agreed on #135.

Claude Code (on behalf of mmcky)

Lenguaje dominante
Shell
Estrellas
0
Forks
1
Merge medio
18 h 51 min
PR fusionados (30 d)
58

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de QuantEcon/actions

Todos los issues de QuantEcon/actions

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.