diff options
| author | Holger Levsen <holger@layer-acht.org> | 2016-11-07 17:15:57 +0100 |
|---|---|---|
| committer | Holger Levsen <holger@layer-acht.org> | 2016-11-07 17:15:57 +0100 |
| commit | d8e50eec1e34209c3f877e2eb7f0113825e1c60d (patch) | |
| tree | 4dfb44e3c2485f268cbd4647c9a6296bd0bc3d60 /README | |
| parent | a1d6b7d8430805c78aad2dceaab68c216e1c7140 (diff) | |
| download | jenkins.debian.net-d8e50eec1e34209c3f877e2eb7f0113825e1c60d.tar.xz | |
reproducible Debian: credit Profitbricks for the new nodes pb11+15+17 (=45 cores and 122G RAM)
Diffstat (limited to 'README')
| -rw-r--r-- | README | 8 |
1 files changed, 5 insertions, 3 deletions
@@ -135,9 +135,11 @@ Installation tests inside chroot environments. * The (current) purpose of https://tests.reproducible-builds.org is to show the potential of reproducible builds for Debian - and six other projects currently. This is research, showing what could (and should) be done... check https://wiki.debian.org/ReproducibleBuilds for the real status of the project for Debian! -* Currently, three suites are tested on 'amd64', 'i386' 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, 16 for 'amd64' and 'i386' each, and 60 for 'armhf', which are each constantly testing packages and saving the results of these tests. +* Currently, three suites are tested on 'amd64', 'i386' 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', 16 for 'i386' and 60 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' and 'i386' we are using two virtual machines each, profitbricks-build(1+5)-amd64 and profitbricks-build(2+6)-i386, which have 18 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 using four virtual machines, profitbricks-build(1+5+11+15)-amd64, which have 15 or 16 cores and 48gb ram each. These nodes are sponsored by link:https://jenkins.debian.net/userContent/thanks.html[Profitbricks]. +** for 'i386' we are using two virtual machines, profitbricks-build(2+6)-i386, which have 18 or 17 cores and 48gb ram each. These nodes are also sponsored by link:https://jenkins.debian.net/userContent/thanks.html[Profitbricks]. ** To test 'armhf' we are using 22 small boards donated by vagrant@d.o: *** five quad-cores (cbxi4a, cbxi4b, and ff4a) with 4gb ram, *** three octo-cores (odxu4, odxu4b and odxu4c) with 2gb ram, @@ -145,7 +147,7 @@ Installation tests inside chroot environments. *** two dual-core (bbx15 and cb3a) with 2gb ram and, *** 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! +* 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'), |