|
|
|
|
|
by ljm
2614 days ago
|
|
I agree with the first part of this. If by CI you mean something like Circle or Google Cloud Build or Travis, then your CI is pretty much limited to whatever you can fit in a YAML file, and what the CI service will support in that. YAML in and of itself is not the easiest thing to parse when you have multiple layers of nesting and a lot of lines. I don't really want to see what a CircleCI config would look like for Nixpkgs. Once you get to the point of scaling your CI you're looking at tailored infrastructure to make sure you're only building what needs to be built. |
|