CloudBees Jenkins Enterprise for Pivotal Cloud Foundry

Note: CloudBees Jenkins Platform for PCF is deprecated, and no further development will be made against this tile.

Resource Requirements

The following table shows the default resource and IP requirements for installing the tile:

Product Resource Instances CPU Ram Ephemeral Persistent Static IP Dynamic IP
CloudBees Jenkins Operations Center 1 2 2048 8192 100000 1 0
CloudBees Jenkins Master 1 2 2048 8192 100000 1 0
CloudBees Jenkins Slave 1 2 2048 100000 0 1 0
CloudBees Jenkins Shared Slave 1 2 2048 100000 0 1 0
CloudBees Compilation 2 2 1024 8192 0 0 1
CloudBees Bootstrap Jenkins with Cloud Foundry 1 1 1024 2048 0 0 1
CloudBees Deregister Jenkins from Cloud Foundry 1 1 1024 2048 0 0 1

Notes

  • You can have 0 or 1 instance of CloudBees Jenkins Operations Center.
  • Each Jenkins Slave is attached to a specific Jenkins Master. For better use of resources, Pivotal recommends that you use Jenkins Shared Slaves instead. These are attached to CloudBees Jenkins Operations Center and leased to Masters when needed.
  • Increasing the instance count for Jenkins Master does not give you High Availability.
Was this helpful?
What can we do to improve?
Create a pull request or raise an issue on the source for this page in GitHub