introduce Lix's buildbot in the infrastructure #125

Merged
raito merged 3 commits from lix-buildbot into main 2024-10-06 09:55:27 +00:00
Owner

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:

  • Fix all remaining secret paths
  • Enroll Lix's buildbot
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: - [x] Fix all remaining secret paths - [x] Enroll Lix's buildbot
raito force-pushed lix-buildbot from 04c5e51feb to 3a6f1c0a3c 2024-10-05 18:16:00 +00:00 Compare
raito changed title from WIP: introduce Lix's buildbot and 2 aarch64 builders in the infrastructure to introduce Lix's buildbot and 2 aarch64 builders in the infrastructure 2024-10-05 18:22:31 +00:00
hexchen approved these changes 2024-10-06 00:19:04 +00:00
hexchen left a comment
Owner

Looks good to me, apart from two nitpicks. Thanks for working on this1

Looks good to me, apart from two nitpicks. Thanks for working on this1
flake.nix Outdated
@ -122,0 +132,4 @@
lixInfraModules = [
{
# This means that anyone with @floral-infra permissions
Owner

C-C C-V mistake? should be @lix-infra

C-C C-V mistake? should be `@lix-infra`
Author
Owner

Yes :'(

Yes :'(
raito marked this conversation as resolved
flake.nix Outdated
@ -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 ];
Owner

would it maybe be sensible to include commonModules in floralInfraModules? seems like a lot of duplication to me on first look.

would it maybe be sensible to include commonModules in floralInfraModules? seems like a lot of duplication to me on first look.
Author
Owner

Good point!

Good point!
raito marked this conversation as resolved
raito force-pushed lix-buildbot from 3a6f1c0a3c to dca8f40678 2024-10-06 08:11:56 +00:00 Compare
raito force-pushed lix-buildbot from dca8f40678 to 04c672c17f 2024-10-06 08:13:41 +00:00 Compare
raito force-pushed lix-buildbot from 574e2f799c to 15be74b9e4 2024-10-06 09:16:07 +00:00 Compare
Author
Owner

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.

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.
Author
Owner

Final (?) preparations are in #130.

Final (?) preparations are in #130.
raito changed title from introduce Lix's buildbot and 2 aarch64 builders in the infrastructure to introduce Lix's buildbot and 1 aarch64 builders in the infrastructure 2024-10-06 09:26:18 +00:00
raito force-pushed lix-buildbot from 15be74b9e4 to b1a7b2c5df 2024-10-06 09:30:34 +00:00 Compare
raito force-pushed lix-buildbot from b1a7b2c5df to 75f97e4cc6 2024-10-06 09:53:42 +00:00 Compare
raito force-pushed lix-buildbot from 75f97e4cc6 to decc9963ee 2024-10-06 09:54:47 +00:00 Compare
raito changed title from introduce Lix's buildbot and 1 aarch64 builders in the infrastructure to introduce Lix's buildbot in the infrastructure 2024-10-06 09:54:50 +00:00
Author
Owner

This is now tested, build02 is left to a further PR when I get console access to it to avoid any breakage.

This is now tested, build02 is left to a further PR when I get console access to it to avoid any breakage.
raito merged commit decc9963ee into main 2024-10-06 09:55:27 +00:00
raito deleted branch lix-buildbot 2024-10-06 09:55:27 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Depends on
Reference: the-distro/infra#125
No description provided.