#15474: Stable CI/CD
----------------------------+----------------------------
Reporter: kallisti5 | Owner: bonefish
Type: bug | Status: new
Priority: high | Milestone: R1/beta2
Component: Build System | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
----------------------------+----------------------------
Comment (by kallisti5):
To help solve this issue, i've been playing with 'concourse-ci' for Haiku.
It's vastly different and solves a *lot* of the problems we have with
buildbot. It also creates a bunch of new issues :-|
Better:
* Container based builds. We build our toolchain into a versioned
container, then all workers use the *exact* same toolchain on all workers.
* Simple YAML configuration of pipelines.
* Pretty modern public web ui
* CLI control and monitoring of builds
* Wide range of "plugins" which are just containers expecting special
inputs/outputs
* Support for branches based on multiple code branches. (r1beta1
toolchain, r1beta1 branch of haiku, etc)
Worse:
* With remote workers, getting random network outages within build
containers
* With remote workers, getting random DNS resolution failures within build
containers.
* WebUI chokes on larger log outputs. I've worked with concourse folks to
help reduce the pain here.
* WebUI can't be put at a different prefix. (build.haiku-os.org/concourse)
* S3 plugin resource is clunky and expects you to use versioned s3
artifacts.
https://ci.haiku-os.org is our current deployment.
There's a lot of promise here, but the network / DNS issues are greatly
slowing the rollout
--
Ticket URL: <https://dev.haiku-os.org/ticket/15474#comment:2>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
