OpenShift CI/CD Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
* nexus pod: 610 MB | * nexus pod: 610 MB | ||
* gogs pod: 110 MB | * gogs pod: 110 MB | ||
=Projects and Jenkins Pods= | |||
<font color=red>Does Jenkins needs its own project, or it can be spun off in an arbitrary project?</font> | |||
=Security Considerations= | =Security Considerations= | ||
Revision as of 20:40, 21 November 2017
External
- https://blog.openshift.com/cicd-with-openshift/, youtu.be demos: 65BnTLcDAJI, wSFyg6Etwx8
- https://github.com/OpenShiftDemos/openshift-cd-demo, https://github.com/OpenShiftDemos/openshift-cd-demo/tree/ocp-3.5
- https://docs.openshift.com/container-platform/3.6/install_config/configuring_pipeline_execution.html
- https://github.com/openshift/jenkins
Internal
Overview
OpenShift provides a certified Jenkins container for building Continuous Delivery pipelines. When necessary, it scales the pipeline execution by on-demand provisioning of multiple Jenkins containers, allowing Jenkins to run many jobs in parallel.
Resources
This is the memory consumption based on a test installation:
- jenkins/jenkins-jnlp pod: 720 MB
- nexus pod: 610 MB
- gogs pod: 110 MB
Projects and Jenkins Pods
Does Jenkins needs its own project, or it can be spun off in an arbitrary project?
Security Considerations
Jenkins components need to access the OpenShift API for various operations: access container images, etc. so they need to be granted sufficient privileges to invoke the OpenShift API for the projects requiring CI/CD pipeline services.
Example: Grant Jenkins Needed Privileges for the Projects that Require CI/CD Services