summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorHolger Levsen <holger@layer-acht.org>2016-03-06 01:05:40 +0100
committerHolger Levsen <holger@layer-acht.org>2016-03-06 01:05:40 +0100
commit29b624b42c82e686a81df23817c3c6c3f1ed3d83 (patch)
tree1cffebe3872fa8aea9842a89fae69e68c3711b70 /README
parent8e39c61031ba0e084f39945c4a0b23ba7f1a8324 (diff)
downloadjenkins.debian.net-29b624b42c82e686a81df23817c3c6c3f1ed3d83.tar.xz
reproducible armhf: reformat
Diffstat (limited to 'README')
-rw-r--r--README7
1 files changed, 6 insertions, 1 deletions
diff --git a/README b/README
index cacdced4..707d7969 100644
--- a/README
+++ b/README
@@ -138,7 +138,12 @@ 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 42 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 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 16 small boards donated by vagrant@d.o: two quad-cores (cbxi4a and cbxi4b) with 4gb ram, three octo-cores (odxu4, odxu4b and odxu4c) with 2gb ram, six quad-cores (wbq0, cbxi4pro0, ff2a, ff2b, opi2a and opi2b) 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!
+** To test 'armhf' we are using 16 small boards donated by vagrant@d.o:
+*** two quad-cores (cbxi4a and cbxi4b) with 4gb ram,
+*** three octo-cores (odxu4, odxu4b and odxu4c) with 2gb ram,
+*** six quad-cores (wbq0, cbxi4pro0, ff2a, ff2b, opi2a and opi2b) 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:
** new untested packages (either uploaded to 'unstable' or 'experimental' or migrated to 'testing'),