I think some of those features on github might incurr a cost. I'm sure we
have more than 500 mb of code.
You could also consider this free openbuild servce
https://build.opensuse.org/
The etherlab guys use it to build debs as per the sticky I put in our
ethercat forum.
They have a connector from github called osc. I tried running it recently
but it uses a Python lib which was deprecated in Python 9.
I don't think the users will be impacted if the end result gets hosted on
http://linuxcnc.org/dists/ as part of the build process.

Rod Webster
*1300 896 832*
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au


On Tue, 15 Nov 2022 at 06:38, Jérémie Tarot <silopo...@gmail.com> wrote:

> Le dim. 13 nov. 2022 à 18:39, Jérémie Tarot <silopo...@gmail.com> a écrit
> :
> >
> > Hello Andy,
> >
>
> Well, at least you're not alone to feel ignored sometimes...
>
> Could someone explain me how relocating the buildbot on someone's
> machine can be better for the project than migrating it to GitHub
> Actions, build farm and package hoster ?
> Don't get me wrong John and Rod, I very much appreciate your proposal
> and investment but I believe your time and resources would be better
> employed. I'm looking at you MesaCT, EtherCAT...
>
> From what I've found and understood, it could be enough to upgrade our
> current ci.yml to use docker containers to build all our packages for
> the desired architectures and selected distributions/releases, and
> then use one of the PackageCloud actions available to push artifacts
> to a specialised host.
> Nothing to ask to anyone, no human dependency, no friendship to
> stretch, all managed openly in main repository, git+gh goodness
> included, all on massively distributed infrastructure... Just missing
> a free beer !
>
> We have enough contacts with other projects already putting this
> tooling to great use, FreeCAD comes to mind first, so we could call
> for advises and directions to ease the process and strengthen the
> output.
>
> Further, Actions marketplace and ecosystem opens a great bunch of
> possibilities for our CI pipeline...
>
> TY
> J
>
>
> _______________________________________________
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>

_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to