The trigger is manual for now, until we get a better idea about stability,
resource usage, etc.
Details
- Reviewers
Alphare pulkit - Group Reviewers
hg-reviewers - Commits
- rHGe917fa36fb58: heptapod-ci: enable pytype checking
Diff Detail
- Repository
- rHG Mercurial
- Branch
- default
- Lint
No Linters Available - Unit
No Unit Test Coverage
Event Timeline
The ci image is defined in this repository : https://foss.heptapod.net/octobus/ci-dockerfiles/
Docker file for the Mercurial CI is here: ci-mercurial-core/Dockerfile
contrib/heptapod-ci.yml | ||
---|---|---|
121 | I would recommand starting with adding when: manual to this so that we can double check the impact and runtime before adding it to the default slow. |
Probably. I know it’s just a matter of adding the right package reference to the Dockerfile, but what builds the image and puts it into the registry? A simple push?
contrib/heptapod-ci.yml | ||
---|---|---|
121 | Will do. Hopefully it can be changed to automatic on stable. For reference, it looks like it's slightly more expensive than a py2 test run: https://foss.heptapod.net/octobus/mercurial-devel/-/pipelines/20813 |
✅ refresh by Heptapod after a successful CI run (🐙 💚)
⚠ This patch is intended for stable ⚠
I would recommand starting with adding when: manual to this so that we can double check the impact and runtime before adding it to the default slow.