End-to-end CI: reusable workflow, run on merge in engine, API and platform
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 56/100
调研方向
Read the GitHub Actions configuration and the linked baseline test issue #52 and Playwright test issue #53 to identify how the apps and scenarios are run. Choose explicit app versions, record those versions with each result, and make the action fail when a scenario breaks. Done means the CI runs both test suites and reports the selected versions.
由索引模型根据 Issue 内容生成。
描述
This issue is part of the epic pyronear/roadmap#11 (End-to-end tests across engine, API and platform).
One GitHub workflow in pyro-envdev runs the whole end-to-end pipeline. Each repo calls it when code is merged on main. The code of the tests stays in pyro-envdev.
In pyro-envdev: a reusable workflow (workflow_call).
- Inputs: the image of each app (engine, API, platform). Default: the latest version of each.
- Steps: start the stack, run the baseline test (pyronear/pyro-envdev#52) and the Playwright tests (pyronear/pyro-envdev#53).
- Output: pass or fail, with the versions used saved with the result, so a failure can be reproduced.
- It also runs in pyro-envdev itself when the tests change, with the latest version of the three apps. Today the CI only checks that the containers start.
In each repo, on merge on main. Example for pyro-api:
- Build the API image from the merged code.
- Call the pyro-envdev workflow with this API image, and the latest engine and platform.
Same in pyro-engine and new-pyro-platform. Each repo must publish its image on every merge on main, so the others can use "the latest version". This last part needs the core team (repo rights and secrets).
Done when
- Reusable workflow in pyro-envdev, with one image input per app
- It runs the baseline and Playwright tests, and fails when a scenario breaks
- Versions used saved with each result
- Each repo publishes its image on merge on
main - Tests run on merge in pyro-api, pyro-engine and new-pyro-platform
Theme Tests · Priority P1 · Period T4-26, T1-27
- 主要语言
- Jupyter Notebook
- 星标
- 1
- 派生
- 3
- 平均合并
- 7 天 11 小时
- 30 天内合并 PR
- 3
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
pyronear/pyro-envdev 的其他 Issue
-
enhancement good first issue help wanted
难度 3/5 1-2 天 新手友好度 64/100
pyronear/pyro-envdev#64 ·
-
enhancement help wanted
难度 3/5 1-2 天 新手友好度 68/100
pyronear/pyro-envdev#63 ·
-
enhancement help wanted
难度 4/5 3-5 天 新手友好度 48/100
pyronear/pyro-envdev#62 ·
-
enhancement good first issue help wanted
难度 3/5 1-2 天 新手友好度 57/100
pyronear/pyro-envdev#61 ·
-
Playwright test: acknowledge an alert可能已有人在做 @princecherry9905 于 3 天前认领。 未关闭enhancement good first issue help wanted
难度 3/5 1-2 天 新手友好度 57/100
pyronear/pyro-envdev#60 · 1 条评论 ·
查看 pyronear/pyro-envdev 的全部 Issue
相似的 Issue
-
ci enhancement good first issue
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 87/100
WordPress/phpunit-test-runner#364 ·
维护者通常 4 天内回复
-
[BUG] deploy.restart_policy without condition drops the restart policy可能已有人在做 @akshat-lakhera 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
docker/compose#14383 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100