summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorHolger Levsen <holger@layer-acht.org>2016-01-05 22:27:08 +0100
committerHolger Levsen <holger@layer-acht.org>2016-01-05 22:27:29 +0100
commitbb73104695c6e87cfacb89b7e9c91c5bacbbe601 (patch)
tree07f5c40e095864cfb2119b5ebb9c8e051eae75e8 /README
parent94115998132d630f6b0b8c532bf17e5b7d14a829 (diff)
downloadjenkins.debian.net-bb73104695c6e87cfacb89b7e9c91c5bacbbe601.tar.xz
reproducible: correct number of cores for amd64 machines
Diffstat (limited to 'README')
-rw-r--r--README2
1 files changed, 1 insertions, 1 deletions
diff --git a/README b/README
index c0b0282d..07b1d8d5 100644
--- a/README
+++ b/README
@@ -139,7 +139,7 @@ Installation tests inside chroot environments.
* Currently, three suites are tested on 'amd64' and 'armhf' architectures: 'testing', 'unstable' and 'experimental'. The tests are done using 'pbuilder' using link:https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain[our toolchain] through concurrent builder jobs, 32 for 'amd64' and 31 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 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].
+** 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 18 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 13 small boards donated by vagrant@d.o: eight quad cores (wbq0, cbxi4pro0, ff2a, ff2b odxu4, odxu4b, odxu4c and opi2a) with 2gb ram, two quad-cores (rpi2b and rpi2c) with 1gb ram and three dual cores (bpi0, hb0 and wbd0) 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: