** for 'amd64' we are using four virtual machines, ionos(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[IONOS].
** for 'amd64' we are using four virtual machines, ionos(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[IONOS].
** for 'i386' we are also using four virtual machines, ionos(2+6+12+16)-i386, which have 10 or 9 cores and 36gb ram each. ionos2+12 run emulated AMD Opteron CPUs and ionos6+16 Intel Xeon CPUs. These nodes are also sponsored by link:https://jenkins.debian.net/userContent/thanks.html[IONOS].
** for 'i386' we are also using four virtual machines, ionos(2+6+12+16)-i386, which have 10 or 9 cores and 36gb ram each. ionos2+12 run emulated AMD Opteron CPUs and ionos6+16 Intel Xeon CPUs. These nodes are also sponsored by link:https://jenkins.debian.net/userContent/thanks.html[IONOS].
** for 'arm64' we are using eight "moonshot" sleds, codethink9-15-arm64, which have 8 cores and 64gb ram each. These nodes are sponsored by link:https://jenkins.debian.net/userContent/thanks.html[Codethink].
** for 'arm64' we are using eight "moonshot" sleds, codethink9-15-arm64, which have 8 cores and 64gb ram each. These nodes are sponsored by link:https://jenkins.debian.net/userContent/thanks.html[Codethink].
** To test 'armhf' we are using 24 small boards hosted by vagrant@reproducible-builds.org:
** To test 'armhf' we are using 26 small boards hosted by vagrant@reproducible-builds.org:
*** six quad-cores (cbxi4a, cbxi4b, ff4a, jtx1a, jtx1b, jtx1c) with 4gb ram,
*** six quad-cores (cbxi4a, cbxi4b, ff4a, jtx1a, jtx1b, jtx1c) with 4gb ram,
*** one hexa-core (ff64a) with 4gb ram,
*** one hexa-core (ff64a) with 4gb ram,
*** two quad-core (virt32a, virt64a) with 15gb ram,
*** two quad-core (virt32a, virt64a) with 15gb ram,
*** two quad-core (virt32b, virt64b) with 7gb ram,
*** two octo-cores (odxu4a, odxu4b) with 2gb ram,
*** two octo-cores (odxu4a, odxu4b) with 2gb ram,
*** eleven quad-cores (wbq0, cbxi4pro0, ff2a, ff2b, odu3a, opi2a, opi2c, jtk1a, jtk1b, p64b and p64c) with 2gb ram, and
*** eleven quad-cores (wbq0, cbxi4pro0, ff2a, ff2b, odu3a, opi2a, opi2c, jtk1a, jtk1b, p64b and p64c) with 2gb ram, and
*** two dual-core (bbx15 and cb3a) with 2gb ram each.
*** two dual-core (bbx15 and cb3a) with 2gb ram each.
** one octo-core with 32GB of ram (divided into two virtual machines running at ~15GB ram each)
** one octo-core with 32GB of ram (divided into two virtual machines running at ~15GB ram each)
** one octo-core with 16GB of ram (divided into two virtual machines running at ~7GB ram each)
* In December 2016 link:https://codethink.co.uk[Codethink] has kindly offered access to 8 arm64 build nodes on link:http://www8.hp.com/us/en/hp-news/press-release.html?id=1800094#.VgQdelox1QI[HP moonshot hardware].
* In December 2016 link:https://codethink.co.uk[Codethink] has kindly offered access to 8 arm64 build nodes on link:http://www8.hp.com/us/en/hp-news/press-release.html?id=1800094#.VgQdelox1QI[HP moonshot hardware].
** 8 cores and 64 GB memory for codethink9-arm64.debian.net used for building arm64 Debian packages for t.r-b.o, running in the future
** 8 cores and 64 GB memory for codethink9-arm64.debian.net used for building arm64 Debian packages for t.r-b.o, running in the future
** 8 cores and 64 GB memory for codethink10-arm64.debian.net used for building arm64 Debian packages for t.r-b.o
** 8 cores and 64 GB memory for codethink10-arm64.debian.net used for building arm64 Debian packages for t.r-b.o