The wheels are merely attached to the job as artifacts. We could
upload them to Heptapod or PyPI, but that's left for a possible followup.
Details
Details
- Reviewers
baymax - Group Reviewers
hg-reviewers
Diff Detail
Diff Detail
- Repository
- rHG Mercurial
- Branch
- default
- Lint
No Linters Available - Unit
No Unit Test Coverage
Event Timeline
Comment Actions
❎ refresh by Heptapod after a failed CI run (🐙 ❤️) https://foss.heptapod.net/octobus/mercurial-devel/-/pipelines/16444
Comment Actions
Do we want to build the wheel for every changeset ? or only build "nightly" build from default? (and tags! for tags !)
What value do you expect if we run them for everything ?
contrib/heptapod-ci.yml | ||
---|---|---|
133 | Should we have an image based on uay.io/pypa/${PLATFORM} with this installed instead ? |
Comment Actions
There seems to have been no activities on this Diff for the past 3 Months.
By policy, we are automatically moving it out of the need-review state.
Please, move it back to need-review without hesitation if this diff should still be discussed.
:baymax:need-review-idle:
Should we have an image based on uay.io/pypa/${PLATFORM} with this installed instead ?