zuul/zuul-website
Code Issues Proposed changes

Add BMW case study

Browse Source 
Change-Id: Ifbbd1a69eec3f43667e9c8f9936af7a2a965c6fe
This commit is contained in:
James E. Blair 2018-08-07 09:36:59 -07:00
parent 9a462490af
commit 034bb57fd5
1 changed files with 32 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
www/users.html
View File

@ -59,6 +59,38 @@
<h2>Zuul Users</h2>
</header>
<h3>
<a href="http://superuser.openstack.org/articles/zuul-case-study-bmw/">
BMW
</a>
</h3>
<p>
BMW has been preparing a centrally hosted CI/CD
instance based on Zuul V3 and many of the projects
using previous CI/CD solutions are already in the
progress of migrating to the new Zuul V3
instance. Hosting many projects on one central
platform has many advantages for operation overhead
and resource sharing in the cloud, but hosting many
projects on one CI/CD instance directly translates to
high stability and availability.
To maximize the availability of their central CI/CD
service, BMW is running
Zuul, <a href="https://zuul-ci.org/docs/nodepool.html">Nodepool</a>
and <a href="https://zookeeper.apache.org/">Zookeeper</a>
services in
an <a href="https://openshift.com/">OpenShift</a>
cluster, hosted on OpenStack. In addition to improved
availability, they have seen several development and
operation benefits for their internal CI/CD
development team.
</p><p>
<a href="http://superuser.openstack.org/articles/zuul-case-study-bmw/">
Read more about BMW at SuperUser.
</a>
</p>
<h3>
<a href="http://superuser.openstack.org/articles/zuul-case-study-godaddy">
GoDaddy