[Qa-jenkins-scm] [Git][qa/jenkins.debian.net][master] some more updates to reflect that our longtime sponsor Profitbricks renamed itself to IONOS

Tue Oct 27 16:29:33 GMT 2020


Holger Levsen pushed to branch master at Debian QA / jenkins.debian.net


Commits:
0782f619 by Holger Levsen at 2020-10-27T17:29:16+01:00
some more updates to reflect that our longtime sponsor Profitbricks renamed itself to IONOS

Signed-off-by: Holger Levsen <holger at layer-acht.org>

- - - - -


3 changed files:

- README
- README.infrastructure
- THANKS.head


Changes:

=====================================
README
=====================================
@@ -14,7 +14,7 @@ https://jenkins.debian.net is a tool for automated quality monitoring of Debian.
 
 Get the source by running `git clone https://salsa.debian.org/qa/jenkins.debian.net`. It's all in there, no (relevant) manual setup has been done besides what's in this git repository. (The irrelevant bits are some very simple configuration files containing passwords.)
 
-The (virtualized) hardware is sponsored since October 2012 by http://www.profitbricks.co.uk - currently it's using more than hundred cores and almost 300 GB memory, thanks a lot!
+The (virtualized) hardware is sponsored since October 2012 by https://www.ionos.com (formerly known as Profitbricks) - currently it's using more than hundred cores and almost 300 GB memory, thanks a lot!
 
 Some stats are available using link:https://jenkins.debian.net/munin/jenkins-month.html[munin-plugins for jenkins].
 
@@ -130,8 +130,8 @@ Installation tests inside chroot environments.
 ** To start all the workers use: `sudo systemctl start reproducible_build at startup.service`
 
 * 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 also using four virtual machines, profitbricks-build(2+6+12+16)-i386, which have 10 or 9 cores and 36gb ram each. pb2+12 run emulated AMD Opteron CPUs and pb6+16 Intel Xeon CPUs. These nodes are also sponsored by link:https://jenkins.debian.net/userContent/thanks.html[Profitbricks].
+** 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[IONOS].
+** for 'i386' we are also using four virtual machines, profitbricks-build(2+6+12+16)-i386, which have 10 or 9 cores and 36gb ram each. pb2+12 run emulated AMD Opteron CPUs and pb6+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, codethink-sled9-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 22 small boards hosted by vagrant at d.o:
 *** six quad-cores (cbxi4a, cbxi4b, ff4a, jtx1a, jtx1b, jtx1c) with 4gb ram,


=====================================
README.infrastructure
=====================================
@@ -19,7 +19,7 @@ root access to all armhf nodes.
 
 === amd64 and i386 nodes
 
-amd64 and i386 nodes run as VMs in the Profitbricks cloud. Mattia and Holger have "physical"
+amd64 and i386 nodes run as VMs in the IONOS cloud. Mattia and Holger have "physical"
 access including remote console and BIOS access.
 
 The VMs for jenkins.d.n and rb-mail1.r-b.o have a statically allocated IP address, as well


=====================================
THANKS.head
=====================================
@@ -2,7 +2,7 @@
 
 === Sponsors
 
- * Since October 2012 jenkins.debian.net has been running on (virtualized) hardware sponsored by link:https://www.profitbricks.co.uk[Profitbricks] - Thanks a lot! Currently we are using:
+ * Since October 2012 jenkins.debian.net has been running on (virtualized) hardware sponsored by link:https://www.ionos.com[IONOS] (formerly known as Profitbricks) - Thanks a lot! Currently we are using:
  ** 23 cores and 75 GB memory for jenkins.debian.net
  ** 15 cores and 48 GB memory for profitbricks-build1-amd64.debian.net used for building amd64 Debian packages for tests.reproducible-builds.org (t.r-b.o)
  ** 10 cores and 36 GB memory for profitbricks-build2-i386.debian.net used for building i386
@@ -18,7 +18,7 @@ Debian packages for t.r-b.o
  ** 2 cores and 8 GB memory for profitbricks-build7-amd64.debian.net used for buildinfos.debian.net
  ** 5 cores and 10 GB memory for profitbricks-build9-amd64.debian.net used for rebootstrap jobs
  ** 4 cores and 12 GB memory for profitbricks-build10-amd64.debian.net used for chroot-installation jobs
- ** 9 cores and 19 GB memory for freebsd-jenkins.debian.net (also running on Profitbricks virtual hardware), used for building FreeBSD for t.r-b.o
+ ** 9 cores and 19 GB memory for freebsd-jenkins.debian.net (also running on IONOS virtual hardware), used for building FreeBSD for t.r-b.o
  * link:https://qa.debian.org/developer.php?login=vagrant%40debian.org[Vagrant] provides and hosts 27 'armhf' systems, used for building armhf Debian packages for t.r-b.o:
  ** four quad-cores with 4 GB RAM each,
  ** three octo-cores with 2 GB RAM each,



View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/commit/0782f619ee75e0e7a9d78319f720b32b39587551

-- 
View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/commit/0782f619ee75e0e7a9d78319f720b32b39587551
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/qa-jenkins-scm/attachments/20201027/93756a17/attachment-0001.html>
