On Wed, Sep 29, 2021 at 2:41 AM Raphaël Gomès <raphael.go...@octobus.net> wrote:
> Hi all, > > I am bringing unfortunate news, though I hope this situation is temporary. > > Earlier this month, OVH which provided free VMs for my company Octobus > has started billing us with no real notice. This wasn't a surprise > however, since we were in a "grace period" of sorts and could expect the > billing to start at any moment, we just hoped it would be later in the > year. > > Four of those VMs were used exclusively for Mercurial's Windows CI in > order to help the project move forward and truly support Windows > (especially on Python 3). Unfortunately, this new regular financial load > adds up on top of the rest of the investment our small company puts into > Mercurial - whether it be developer time for projects like Heptapod or > directly on Mercurial like bug fixes, code review, etc. - and is not > sustainable for us at the moment. > > I have already stopped two of the four machines earlier this week and > will remove the last two tomorrow (30th of September), meaning that we > will not have any regular Windows CI for the project anymore. > > I've sent https://phab.mercurial-scm.org/D11499 to adjust the CI file to > not break every pipeline from now on, hopefully it can be queue before > that. > > We're trying to figure out ways of gaining back Windows VMs (and > actually for other OSes as well) in a more sustainable manner, if you > know of anyone that could help, please reach out. > I've been running https://ci.hg.gregoryszorc.com/ for the past few years out of my own pocket. I was actually thinking about turning it off since it seems to be redundant with the superior Octobus CI and it is costing me a good chunk of money. But maybe I should keep it around? What's the monthly cost to run the Windows CI workers? How many CPU cores / memory do you need? What's the total CPU/wall time we're talking about here? If we cut down Windows CI to just run on pushes to hg-committed, I feel like we can reduce the cost to something reasonable. (Feel free to drop the list if you want to discuss privately.)
_______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
