From 2f83ac7d3dde82be6f99f4e929830daa2b1dc257 Mon Sep 17 00:00:00 2001 From: Holger Levsen Date: Mon, 12 Oct 2015 23:38:34 +0200 Subject: reproducible: explain new amd64 nodes --- README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'README') diff --git a/README b/README index 2f2b946a..baaf6012 100644 --- a/README +++ b/README @@ -139,7 +139,7 @@ Installation tests inside chroot environments. * Currently, three suites are tested on amd64: 'testing', 'unstable' and 'experimental'. The tests are done using 'pbuilder' using link:https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain[our toolchain] through concurrent builder jobs, 16 for 'amd64' and 8 for 'armhf', which are each constantly testing packages and saving the results of these tests. -** These builds on remote nodes run on very different hardware: for 'amd64' we are now using two hosts, profitbricks-build1-amd64 profitbricks-build2-amd64, which have 14+15 cores and 42gb ram each and are sponsored by Profitbricks. +** These builds on remote nodes run on very different hardware: for 'amd64' we are now using four virtual machines, profitbricks-build(1+2+5+6)-amd64, which have 16 or 17 cores and 48gb ram each and are sponsored by link:https://jenkins.debian.net/userContent/thanks.html[Profitbricks]. ** To test 'armhf' we are using four small boards donated by vagrant@d.o: two quad cores (wbq0 and cbxi4pro0) with 2gb ram and two dual cores (bpi0 and hb0) with 1gb ram, each. We would love to have more or more powerful ARM hardware in the future, if you can help, please talk to us! * Packages to be build are scheduled in the SQLite database via a scheduler job, which runs every hour and if the queue is below a certain threshold schedules four types of packages: -- cgit v1.2.3-54-g00ecf