----- Mail original ----- > De: "Hartmut Goebel" <h.goe...@crazy-compilers.com> > À: "mercurial" <mercurial@lists.mercurial-scm.org> > Envoyé: Samedi 5 Octobre 2024 16:26:41 > Objet: Re: Producing Mercurial wheels from Github Actions + modernize build > process
> Am 04.10.24 um 22:25 schrieb PIERRE AUGIER: > > - a tiny repo on Githut (basically only a README, license and workflow > files) with a workflow triggered by foss.heptapod.net which downloads > the sdist, builds the wheels and tests them. > > Why do you want to use github, which is a proprietary platform? > > gitlab/heptapod provides all you need, too. And since the .gitlab-ci.yml can > be > part of the hg repository, there is no need to fiddle with triggering jobs on > external platforms. And the build jobs can check out the hg repo if desired. foss.heptapod.net have no runners for Windows and the different flavors of macOS. Setting such runners would be possible but would cost time and money. Mercurial needs to improve on few basic points to continue to be a reasonable alternative to Git in 2024 (https://bz.mercurial-scm.org/show_bug.cgi?id=6923). Github Actions is very convenient to build the wheels on all mainstream platforms. Please tell me how we could do that with gitlab/heptapod or any other open-source platform? Best, Pierre _______________________________________________ Mercurial mailing list Mercurial@lists.mercurial-scm.org https://lists.mercurial-scm.org/mailman/listinfo/mercurial
