* 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.
* 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].
** 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 quadcores (cbxi4a and cbxi4b) with 4gb ram, nine quadcores (wbq0, cbxi4pro0, ff2a, ff2b odxu4, odxu4b, odxu4c, opi2a and opi2b) with 2gb ram, two quad-cores (rpi2b and rpi2c) with 1gb ram and three dualcores (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:
* 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'),
** new untested packages (either uploaded to 'unstable' or 'experimental' or migrated to 'testing'),
** 3 cores and 6 GB memory for freebsd-jenkins.debian.net (also running on Profitbricks virtual hardware)
** 3 cores and 6 GB memory for freebsd-jenkins.debian.net (also running on Profitbricks virtual hardware)
* link:https://qa.debian.org/developer.php?login=vagrant%40debian.org[Vagrant] provides and hosts 16 'armhf' systems:
* link:https://qa.debian.org/developer.php?login=vagrant%40debian.org[Vagrant] provides and hosts 16 'armhf' systems:
** two quad-cores with 4 GB RAM each,
** two quad-cores with 4 GB RAM each,
** nine quad-cores with 2 GB RAM each,
** three octo-cores with 2 GB RAM each,
** six quad-cores with 2 GB RAM each,
** two quad-cores with 1 GB RAM and
** two quad-cores with 1 GB RAM and
** three dual-cores with 1 GB RAM.
** three dual-cores with 1 GB RAM.
* link:https://letsencrypt.org[Let's encrypt] provides free of charge SSL certificates for jenkins.debian.net, reproducible.debian.net and tests.reproducible-builds.org.
* link:https://letsencrypt.org[Let's encrypt] provides free of charge SSL certificates for jenkins.debian.net, reproducible.debian.net and tests.reproducible-builds.org.
