CloudBees Core for Pivotal Platform is deployed to Pivotal Container Service (PKS) using standard Kubernetes manifests. Upon installation, CloudBees Core Cloud Operations Center runs in a Kubernetes Pod and its user interface will be available from a web browser. Administrators can then integrate Operations Center with an Identity Provider, such as LDAP, for authentication, and enable CloudBees Role-based Access Control (RBAC) for authorization. Operations Center is then used to provision Managed Master Pods, which support the CI/CD workloads of each team using CloudBees Core. Each Managed Master may provision Kubernetes Pods on demand in order to run CI/CD Pipelines, like building, testing, and deploying an app.
CloudBees Core™, based on Jenkins®, extends Jenkins with functionality that embeds best practices, rapid onboarding, security and compliance. Deep integrations with cloud platforms like Pivotal Platform through Pivotal Container Service (PKS) allow the shared services and DevOps teams to follow standard protocols to deploy and manage CloudBees Core for Pivotal Platform like any other business-critical application.
Regardless of what type of application you are delivering—Java, mainframe, .NET—CloudBees Core is a CI/CD solution for all your application environments.
Work with Modern & Legacy Apps
Run modern apps on a cloud-native architecture for scalability and elasticity. Legacy apps can also benefit by utilizing the power of Kubernetes via Pivotal Container Service for CI/CD workloads.
Mitigate Risk with Security & Compliance
CloudBees role-based access control plus additional security features enable permissions to be defined by user, team, agents, folders and jobs.
While Jenkins® is the leading automation platform for Continuous Integration (CI) and Continuous Delivery (CD), enterprises need to scale CD to a multitude of teams without increasing the administrative burden. In addition, they need to ensure security and compliance without inhibiting productivity. Finally, enterprises have diverse software portfolios that may consist of modern applications utilizing a microservices architecture with containers, as well as applications built on outdated technology that can all benefit from one CI/CD solution.
CloudBees Core™ is a CI/CD automation engine with the flexibility to support diverse software portfolios and the unified governance required by growing organizations. Based on Jenkins, CloudBees Core extends Jenkins with functionality that embeds best practices, rapid onboarding, security and compliance. It provides a shared, centrally-managed CI/CD service but delivers a self-service experience for engineering teams.
CloudBees Core on modern cloud platforms is a cloud native CI/CD solution that leverages Kubernetes and includes an elegant UX for rapid onboarding and configuration. Customers benefit from the ability to run workloads for a range of application types on a scalable and highly available CloudBees Core cluster. When you run CloudBees Core on Kubernetes platforms such as Pivotal Container Service (PKS) on Pivotal Platform or Google Kubernetes Engine (GKE), your CI/CD workloads benefit from lightweight Jenkins agent containers that autoscale to the demands of large enterprise software development teams.
Deep integrations with cloud platforms like Pivotal Platform allow the shared services and DevOps teams to follow standard protocols to deploy and manage CloudBees Core for Pivotal Platform like any other business-critical application. The IT operations team can provision a CloudBees Core cluster in seconds and configure tight access controls to conform to IT security standards.
Option to create and destroy the service instances on demand, as required
Automate periodic backups and allow for restoring from a backup if needed
Plan migrations. Developers can resize deployments by changing their service plans as needs and resource requirements change.
Version choice: Operators can let developers to choose between multiple versions of the software when creating an instance
The service is documented with instructions for setup and operation
Supports high availability against internal service failures to minimize downtime for bound applications
Multi-Availability Zone support: Make use of multiple availability zones in cloud deployments to support failover
Quotas: Operators can place limits on service instance counts
Developers have control over when to upgrade to new versions, subject to policies set by operators, so that app modifications and downtime can be managed
Supports offline use without dependencies on externally running services or licensing validation
"This new offering creates a unique value for our existing and potential future customers while expanding our options. Deep integrations with cloud service providers like Pivotal Platform through Pivotal Container Service allow DevOps teams to manage CloudBees Core like any other business-critical application."
Jason Mero, VP of business development at CloudBees
Contact us about CloudBees Core for Pivotal Platform.