introduce Lix's buildbot in the infrastructure #125
No reviewers
Labels
No labels
Compat/Breaking
Difficulty
Architectural
Difficulty
Easy
Difficulty
Hard
Help Wanted
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Security
Silenced Alert
Status
Abandoned
Status
Blocked
Status
Need More Info
Status
Postponed
Tracking Issue
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Depends on
#126 feat: prepare for Lix machines
the-distro/infra
Reference: the-distro/infra#125
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "lix-buildbot"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As part of our governance decision, we are moving slowly Lix infrastructure in this repository.
This makes the Lix infrastructure code public and benefit from the Floral project sysadmin efforts.
TODO:
04c5e51feb
to3a6f1c0a3c
WIP: introduce Lix's buildbot and 2 aarch64 builders in the infrastructureto introduce Lix's buildbot and 2 aarch64 builders in the infrastructureLooks good to me, apart from two nitpicks. Thanks for working on this1
@ -122,0 +132,4 @@
lixInfraModules = [
{
# This means that anyone with @floral-infra permissions
C-C C-V mistake? should be
@lix-infra
Yes :'(
@ -141,3 +174,1 @@
buildbot.imports = commonModules ++ [ ./hosts/buildbot ];
public01.imports = commonModules ++ [ ./hosts/public01 ];
build-coord.imports = commonModules ++ [ ./hosts/build-coord ];
bagel-box.imports = floralInfraModules ++ commonModules ++ [ ./hosts/bagel-box ];
would it maybe be sensible to include commonModules in floralInfraModules? seems like a lot of duplication to me on first look.
Good point!
3a6f1c0a3c
todca8f40678
dca8f40678
to04c672c17f
574e2f799c
to15be74b9e4
A part of it was sent in #129, build02 will probably be extracted as well.
All that remains is the Buildbot which is arguably non-trivial to migrate as it implies also a big upgrade in terms of buildbot-nix code, buildbot code, etc.
Final (?) preparations are in #130.
introduce Lix's buildbot and 2 aarch64 builders in the infrastructureto introduce Lix's buildbot and 1 aarch64 builders in the infrastructure15be74b9e4
tob1a7b2c5df
b1a7b2c5df
to75f97e4cc6
75f97e4cc6
todecc9963ee
introduce Lix's buildbot and 1 aarch64 builders in the infrastructureto introduce Lix's buildbot in the infrastructureThis is now tested, build02 is left to a further PR when I get console access to it to avoid any breakage.