Peter Gutmann via cfarm-users <cfarm-users@lists.tetaneutral.net> writes:
> Is anyone doing CI-style automated deployment across multiple cfarm hosts, or > more generally on systems where all you've got to play with are SSH, sh/bash, > and a compiler? Conventional approaches seem to require installing CI agents > on each target system (and Docker, and cloud access, and ...), I was looking > for something that works purely through client-side SSH without requiring > system changes on a wide range of very different target systems (this is also > useful for testing on oddball SBCs on a local network running obsolete and > obscure OSes). Pipelight looks like a promising candidate, is anyone using > that > with cfarm hosts, or do you know of another solution? I thought this usage was against the recommended use of the cfarm, but I cannot find a reference now -- was the acceptable use policy modified? FWIW, ready-to-use GitLab CI/CD shared runners for exotic architectures would be a great contribution. Is anyone aware of a project that offer this? I have both hardware and sysadmin cycles available to help with it, but my level of involved is usually stachastic so I would prefer to piggy back on someone else's effort. Is it acceptable to run that on the cfarm? Perhaps only on some of the more heavy machines? I would add my own projects to that, if available. Since commits are rare (<100/year) I wouldn't expect a lot of build churn anyway. /Simon PS. Autobuild -- https://www.nongnu.org/autobuild/ -- is an old project providing infrastructure for the kind of setup you describe. It requires your own scripting for invoking jobs and gathering logs, so may not be exactly what you were looking for.
signature.asc
Description: PGP signature
_______________________________________________ cfarm-users mailing list cfarm-users@lists.tetaneutral.net https://lists.tetaneutral.net/listinfo/cfarm-users
