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

オープン
  • 何か問題がありますか？
#302 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
github-actions, shell
領域
ci-cd

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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)

主要言語
Shell
スター
0
フォーク
1
平均マージ
18時間 51分
マージ済み PR（30日）
58

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

QuantEcon/actions のほかの issue

QuantEcon/actions の issue をすべて見る

似ている issue

Shell/Bash の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。