diff options
| author | Holger Levsen <holger@layer-acht.org> | 2016-02-03 02:28:37 +0100 |
|---|---|---|
| committer | Holger Levsen <holger@layer-acht.org> | 2016-02-03 02:28:37 +0100 |
| commit | a77ecd79d9468cdcb851a7222905e03e3bf1a990 (patch) | |
| tree | be0b3de2d87374df2a6e68180867af3289e6ca62 /README | |
| parent | c6eea02241ea847c0f112b04e309705f3bed7af2 (diff) | |
| download | jenkins.debian.net-a77ecd79d9468cdcb851a7222905e03e3bf1a990.tar.xz | |
reproducible armhf: add new armhf node, thanks to Vagrant
Diffstat (limited to 'README')
| -rw-r--r-- | README | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -140,7 +140,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 34 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 14 small boards donated by vagrant@d.o: nine quad cores (wbq0, cbxi4pro0, ff2a, ff2b odxu4, odxu4b, odxu4c, 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 15 small boards donated by vagrant@d.o: ten quad cores (wbq0, cbxi4a, cbxi4pro0, ff2a, ff2b odxu4, odxu4b, odxu4c, 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'), |