This is just a little prep for the SQS BuildQueue implementation. Conveyor now has two subcommands:
conveyor server: Only runs the http server that enqueues build requests.
conveyor worker: Runs a configurable number of workers (defaulting to runtime.NumCPU) that will pop jobs from the build queue and perform the build using a docker daemon.
Invoking conveyor without any subcommands will yield the previous behavior and start both the server and the workers.
There's also a --queue flag now, but the only option available is memory://.
After the SQS implementation is added, this will allow you to split Conveyor apart using a setup like this:
benguillet
commented
8 years ago
This is just a little prep for the SQS BuildQueue implementation. Conveyor now has two subcommands:
conveyor server: Only runs the http server that enqueues build requests.conveyor worker: Runs a configurable number of workers (defaulting to runtime.NumCPU) that will pop jobs from the build queue and perform the build using a docker daemon.Invoking
conveyorwithout any subcommands will yield the previous behavior and start both the server and the workers.There's also a
--queueflag now, but the only option available ismemory://.After the SQS implementation is added, this will allow you to split Conveyor apart using a setup like this: