dave on Nostr: npub19amud…hqjn6 this is awesome! I haven't yet explored making a channel within a ...
npub19amud7rggjx0u77wqqa84x537x7g5nws9pqdgu5qadgypfreyv2s5hqjn6 (npub19am…qjn6) this is awesome! I haven't yet explored making a channel within a project repo, but I want to try that soon. Looks very useful.
Noticed a small typo: "run jobs n a Docker image"
If I could offer an alternative take on Gitlab CI setup: Use 'guix pack' to produce an image that has just the dependencies needed to build and run the project. This trades flexibility for speed. The CI jobs don't have to redundantly download the same dependencies over and over because they are already there. However, the image needs to be periodically updated with a fresh build when dependencies are modified. We use this approach for guile-hoot because we don't want the overhead of running a substitute server but we need both a custom built Guile and V8 and it would take hours to know if your branch is green if CI had to build those each time.
Noticed a small typo: "run jobs n a Docker image"
If I could offer an alternative take on Gitlab CI setup: Use 'guix pack' to produce an image that has just the dependencies needed to build and run the project. This trades flexibility for speed. The CI jobs don't have to redundantly download the same dependencies over and over because they are already there. However, the image needs to be periodically updated with a fresh build when dependencies are modified. We use this approach for guile-hoot because we don't want the overhead of running a substitute server but we need both a custom built Guile and V8 and it would take hours to know if your branch is green if CI had to build those each time.