#15474: Stable CI/CD
--------------------------+------------------------------
Reporter: kallisti5 | Owner: bonefish
Type: bug | Status: new
Priority: high | Milestone: R1/beta2
Component: Build System | Version: R1/Development
Keywords: | Blocked By:
Blocking: | Has a Patch: 0
Platform: All |
--------------------------+------------------------------
We use buildbot at the moment for our releases. While it has worked over
the years, we have been slowly outgrowing it. We have 1000+ lines of
python code using the Buildbot API.
Some limitations of our current buildbot:
* Branch selection broken. Unable to inject multiple codebases into a
build without a major refactor.
* Continuous series of CVE's we have to keep bumping the buildbot version
to resolve.
* (opinion) buildbot is lacking maintainers. A lot of major bugs have
crept in recent releases which have been breaking our builds.
Here are some of the pain points from a design standpoint:
* buildtools / toolchains are compiled on each builder and stored locally.
It's possible to get a random toolchain depending on your random builder
assignment.
* Since buildtools / toolchains are cached, we don't support "selecting
buildtools branches"
* Secrets don't work in all API objects preventing their proper usage.
* We can't send artifacts to buildbot using the native API's. Our
artifacts are too big and break the buildbot web ui during the upload.
(builders timeout)
--
Ticket URL: <https://dev.haiku-os.org/ticket/15474>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
