OpenShift CI/CD Operations: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 30: | Line 30: | ||
=Organizatorium= | =Organizatorium= | ||
The Jenkins container must be able to access the OpenShift API: | The Jenkins container must be able to access the OpenShift API: |
Revision as of 16:45, 1 November 2017
Internal
Overview
Set Up a Jenkins CI/CD Pipeline
Create Required Image Streams
Create Required Projects
Create the following projects:
1. A project for the CI/CD components, named "cicd":
oc new-project cicd --display-name="CI/CD pipeline with Jenkins"
2. A project to host development-stage containers and processes, named "dev":
oc new-project dev --display-name="Tasks - Dev"
3. A project to host publicly-accessible application produced by the CI/CD pipeline, named "stage":
oc new-project stage --display-name="Tasks - Stage"
Organizatorium
The Jenkins container must be able to access the OpenShift API:
oc policy add-role-to-user edit system:service account:cicd:default -n cicd oc policy add-role-to-user edit system:service account:cicd:default -n cicd-dev oc policy add-role-to-user edit system:service account:cicd:default -n cicd-stage
oc project cicd
Instantiate components. Use templates. 'cicd-github-template.yaml'.
oc process -f https://raw.githubusercontent.com/OpenShiftDemos/openshift-cd-demo/master/cicd-github-template.yaml | oc create -f -
Inspect Nexus
Inspect Jenkins