Changes between Version 14 and Version 15 of Questions and Answers

Timestamp:

04/29/25 22:17:55 (4 weeks ago)

Author:

enno

Comment:

--

Questions and Answers

@@ -44 +44 @@
 == CI / CD
 
-'''Q:''' How do I guarantee that newer package versions are available on CI / CD?
+Q: How can I ensure newer package versions are available on my air-gapped CI/CD server (and build them there)?
 
-'''A:''' There are several steps involved
+A:
+If you want to build everything from source on the CI/CD server, you must transfer:
 
-----
+Updated package definitions (e.g., new Guix commit / channel state)
+All required source code (not binaries)
 
-* Step 1
+Step 1: On a networked (twin) machine
+a) Check for new versions
 
-Run 
+guix refresh PACKAGE-NAME
+This will update the local package definition in your channel checkout (if you're maintaining your own channels or overlay packages).
 
-{{{#!sh
-guix refresh
-}}}
+b) Build the package to pull source code into the store
 
-on a twin machine to check for new package versions.
+guix build --source PACKAGE-NAME
+This ensures that all source tarballs and patches are downloaded and cached.
 
-----
+c) Export source code and channel state
 
-* Step 2
+Export the source derivation (not the binaries!):
 
-Run
+guix archive --export -r $(guix build --source PACKAGE-NAME) > sources.nar
+Also export the updated Guix channels or commit used:
 
-{{{#!sh
-guix graph
-}}}
+guix describe --format=channels > channels.scm
 
-on the output of guix refresh to find dependencies.
+Step 2: Transfer to the air-gapped CI/CD server
+Copy the following files via USB or other air-gap-compliant method:
 
-----
+sources.nar (the archive of source derivations)
+channels.scm (to sync channel state)
+Optionally: your custom channel checkout (if using overlays)
 
-* Step 3
+Step 3: On the CI/CD server
+a) Sync channel state
 
-Copy related source packages to CI / CD via USB drive
+guix time-machine -C channels.scm -- build PACKAGE-NAME
+Or, if you want to pull into your main Guix:
 
-----
+guix pull --channels=channels.scm
+b) Import the sources
+
+guix archive --import < sources.nar
+Now the CI/CD server has all it needs to build the package from source without network access.
+
+Optional: Preload additional sources or dependencies
+To avoid surprises, you may want to pre-fetch all sources recursively:
+
+guix build --sources=transitive PACKAGE-NAME
+guix archive --export -r $(guix build --sources=transitive PACKAGE-NAME) > all-sources.nar
+This ensures no source fetch attempts will occur during CI builds.
 
 [WikiStart Back]