| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
| |
No idea what this stuff is, but modify it with the intent of allowing building
just the sources related to the agent, if guile-fibers is missing.
This should make it easier to avoid problems in Guix where things like
guile-fibers are currently broken for aarch64-linux, and also avoid having a
load of perl dependencies for the agent, which doesn't use sqitch.
|
| |
|
|
|
| |
This is untested, but might be quite cool for running a single agent instance
of the build coordinator, all in one process.
|
| | |
|
| |
|
|
| |
So that the client part doesn't depend on fibers.
|
| |
|
|
|
| |
To start making it possible to use the agent, without having to load anything
related to fibers (as it doesn't work on the hurd yet).
|
| |
|
|
| |
To install the sqitch data and README.org.
|
| |
|
|
| |
Which was extracted from the Guix Build Coordinator.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
There were a few issues with the previous approach, I was concerned about
trying to write to the SQLite database from two processes, it's already
segfaulting occasionally when accessing it from just one. Additionally, the
client actions were already doing things that should happen in the coordinator
process, like allocating builds.
I'm trying to not turn this in to a web app, but not doing very well. Although
having this information and these actions available over the network does make
it possible to build a web app frontend, which I've had in mind.
|
| |
|
|
| |
To produce Prometheus style metrics for the counts of various things.
|
| |
|
|
| |
As that is an easy way to find things to build.
|
| | |
|
| | |
|
| |
|
|
| |
It seems to cause problems, as it's defined in guile.am as well.
|
|
|
Setup done with the aid of [1].
1: https://www.draketo.de/proj/with-guise-and-guile/guile-projects-with-autotools.html
|