#15474: Stable CI/CD
----------------------------+----------------------------
Reporter: kallisti5 | Owner: kallisti5
Type: bug | Status: closed
Priority: critical | Milestone: R1/beta2
Component: Build System | Version: R1/Development
Resolution: fixed | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
----------------------------+----------------------------
Changes (by kallisti5):
* status: assigned => closed
* resolution: => fixed
Comment:
Agree. The new build system is in place. There is only one worker at the
moment (a Dell i7 in my office), but it is a pretty strong machine with
lots of RAM and an NVMe. (Donated by Haiku, Inc.) Waiting on Geist to get
some freetime so we can walk through configuring his systems.
We can build branches (and have branch-based buildtools, etc). All workers
use an identical set of binary buildtools from docker, and anyone is free
to pull the pre-compiled buildtools and use them on their desktop. (I
could see folks now doing Windows / OS X builds within these toolchain
containers as well.. only requirement is Docker)
All the pipelines are in our infrastructure git, buildbot has been
disabled, links have been updated. Branch images upload to their
associated S3 buckets at Wasabi which cuts down on costs and speeds
downloads. Images (and the Haiku repo itself) is signed now as well with
minisign (.minisig)
There are the occasional DNS issues, Concourse is working to move to plain
containerd which will hopefully solve the issues.
--
Ticket URL: <https://dev.haiku-os.org/ticket/15474#comment:6>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
