That makes it consistent with the guix-daemon settings.
* hydra/modules/sysadmin/build-machines.scm (berlin-new-build-machine-os):
Use MAX-JOBS as the number of Cuirass workers.
* hydra/nginx/berlin.scm (languages-to-accept): New list. Move here
the languages list from ...
(%extra-content) ... here. Use languages from 'languages-to-accept'.
(guix.gnu.org-redirects-for-each-language): New procedure. Add
new video redirections.
(guix.gnu.org-redirect-locations): New list. Move here the
old redirections.
(guix.gnu.org-other-locations): New list. Move here the other nginx
locations from ...
(guix.gnu.org-locations): ... here. Reimplement in terms of the above.
* hydra/nginx/html/bordeaux/index.html: (Using these substitutes):
Fixed a typo, and added a how to code snippet for users of guix system.
Signed-off-by: Christopher Baines <mail@cbaines.net>
* hydra/bayfront.scm (operating-system)[services]: Change the
guix-build-coordinator-queue-builds-configuration to include i586-gnu
and cross builds to i586-pc-gnu.
* hydra/nginx/html/bordeaux/index.html: New file.
* hydra/bayfront.scm (%bayfront-nginx-service-extra-config): Remove
proxy config relevant for hydra.
(%bordeaux.guix.gnu.org-nginx-servers): Serve log files, and show log
files for /build/UUID requests. Also service an index.html page.
(operating-system)[services]: Use a custom nginx package built with a
couple of additional modules.
This is used when deciding whether the outputs from a build should be
submitted.
* hydra/bayfront.scm (%guix-build-coordinator-configuration)[hooks]:
Specify a build-submit-outputs-hook.
* hydra/milano-guix-1.scm (operating-system)[file-systems]: Mount /tmp
as a tmpfs, to hopefully speed up builds.
[swap-devices]: Add /dev/sdb2.
[services]: Disable SSH password authentication, and switch bayfront
to bordeaux in a couple of places.
* hydra/bayfront.scm (%bordeaux.guix.gnu.org-nginx-servers): New
variable.
(servers)[nginx-service-type]: Add
%bordeaux.guix.gnu.org-nginx-servers to the server blocks list.
Make the Guix Build Coordinator agent more gentle, reducing the max
parallel builds and decreasing the load average limit. Also reduce the
default max-jobs at the daemon level (for builds happening not through
the coordinator agent), and set the default cores to 24 to avoid one
build from loading all the cores.
* hydra/bayfront.scm (services)[guix-build-coordinator-agent-service-type]:
Tweak max-parallel-builds and max-1min-load-average.
[guix-service-type]: Tweak the extra-options.
This is to be used for substitutes, currently served from bayfront.
* hydra/modules/sysadmin/dns.scm (guix.gnu.org.zone): Add entry for
bordeaux.guix.gnu.org.
Berlin doesn't build much stuff anymore, and removing transient cache failures
require manual intervention.
* hydra/modules/sysadmin/services.scm (guix-daemon-config): Do not cache failures.
And update the about.txt boilerplate text.
* doc/release.org (Update the on-line copy of the manual): Add a note
about restarting mcron after reconfiguring.
(Prepare the email announcement): Add usage instructions for
announce-gen. Reword to explicit that appending NEWS should have been
handled by the announce-gen script.
* doc/release.org (Bootstrap and build): Renamed from 'Bootstrapping'.
Use nproc * 2 as the parallel job count passed to make.
(Update the translation files): Renamed from 'Updating the translation
files'. Suggest running 'autoreconf -f' after updating the
translations to catch mistakes and cross-reference the guix manual.
Drop last paragraph, which isn't that important anymore now that the
translations are fetched from git and not rate limited.
(Run “make release” for one or several release candidates): Simplify
wording.
(Merge the version-X-Y-Z branch into master): New section.
(Update web pages): Note mcron frequency.
(Prepare the email announcement): Use X.Y.Z version templates.
(Send the email announcement): Drop the newsgroups. Publicly
available NNTP servers seem a rarity these days.
(Post a news item on the web site (automated)): Drop recommendations
about the form, as this is now all automated.
I had forgotten to update the command used for the release GNU FTP as
well.
* doc/release.org (Upload all the files) <gnupload>: Include the
.qcow2 and .iso release files.
* doc/release.org (Run “make release” for one or several release
candidates): Update the list of the required offload machine
architectures. Mention that QEMU user (transparent) emulation is
likely not good enough.
* doc/release.org (Upload all the files): Mention where the script
originates and that it requires the ncftp package. In the examples,
change directory to the release directory, as file names containing
slashes are rejected by the server.
Those machines are unreachable and should be made available through Wireguard
when back online.
* hydra/machines-for-berlin (overdrive): Remove unreachable machines.
Also mention the CPU they use and the amount of physical memory they
have. Likewise for the Softiron Overdrive 1000.
* hydra/machines-for-berlin.scm (overdrive): Mention CPU model and RAM.
(armv7): Likewise for the BeagleBoard.
* doc/release.org (Updating the translation files): Remove the
paragraphs detailing what do when starting from a pristine tree, as
this is what the 'Bootstrap' section now already covers.
(Run “make release” for one or several release candidates): Rename
GuixSD to Guix System.
This may be obvious in hindsight, but running 'make release' without
having run 'make' would lead to a confusing problem where the user's
guix command (a wrapper) would be used instead of scripts/guix,
leading to an erroneous GUILE_LOAD_PATH.
It would lead to using an older version of the guix package to build
the release artifacts.
* doc/release.org (Bootstrapping): Suggest running make.
This is required for offloading.
* hydra/keys/guix/maxim-desktop-export.pub: New key.
* hydra/modules/sysadmin/overdrive.scm (%authorized-guix-keys):
Authorize it.
This is so that I can use overdrive1 as an offload machine.
* hydra/modules/sysadmin/overdrive.scm (%accounts) [maxim]: New
sysadmin account.
(overdrive-system) [service] <openssh-service-type>: Authorize my
public SSH key.
