Introduce a new component: worker which performs the real builds

bazooka-ci / bazooka

Continuous Integration and Continuous Deployment Server

http://docs.bazooka-ci.io/

MIT License

60 stars 5 forks source link

Introduce a new component: worker which performs the real builds #260

Open jawher opened 9 years ago

jawher commented 9 years ago

through a queue (using beanstalkd)

Only server now has access to mongo. All other components go through the REST api.

The build log is now captured using the syslog logging driver for dockeOnly server now has access to mongo. All other components go through the REST api.

The build log is now captured using the syslog logging driver for docker

jawher commented 9 years ago

WARNING This PR needs docker experimental features, mainly syslog-tag support, which was merged after the 1.7 release.

What remains to be done:

[ ] Use the server syslog url env var instead of hard coded docker0 bridge
[ ] Rework the global SCM key management
[ ] Handle slots (fixed number of parallel builds)
[ ] Make the CLI manage a beanstalk container (besides server, web and mongo)
[ ] Add cli worker sub-command to be able to start a worker container

jawher commented 9 years ago

I'm working on splitting the work done here into smaller and more manageable pull requests. I can see 3 macro parts:

Use syslog to collect logs
Let all components (orch, parser and lang parsers) call the server API instead of mongo to manage builds
Extract the concrete build part to a worker component