openshift
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| openshift [2018/02/21 10:43] – [OpenShift CICD] skipidar | openshift [2020/12/27 20:35] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 164: | Line 164: | ||
| Security. Builds and runs are executed as root, which may be exposed. S2I can execute commands with less rights. | Security. Builds and runs are executed as root, which may be exposed. S2I can execute commands with less rights. | ||
| + | |||
| + | </ | ||
| + | | Image Stream |< | ||
| + | Docker images from different sources, identified by the same tag. \\ | ||
| + | Can be monitored, to trigger a build as a result. | ||
| + | </ | ||
| + | | Jenkins pipeline |< | ||
| + | * A Jenkins can be used to build artifacts via OPenShift. | ||
| + | * A Jenkins strategy is chose in BuildConfig | ||
| + | * A Jenkins-Pipeline is defined as code in BuildConfig | ||
| + | |||
| + | During the build the following will then happen | ||
| + | * A Jenkins will be started in a container and reused by all Jobs with the Jenkins-build-strategy. | ||
| + | * A Pipeline will be created. | ||
| + | * An image will be build. | ||
| + | * An image will be put into the registry. | ||
| + | * Then optionally, via trigers, the pod can be replaced by new pods with the container from new image. | ||
| + | |||
| + | Build via OpenShift pipelines: | ||
| + | {{https:// | ||
| + | |||
| + | More: | ||
| + | https:// | ||
| + | </ | ||
| + | | XXX |< | ||
| + | </ | ||
| + | | XXX |< | ||
| + | </ | ||
| + | | XXX |< | ||
| </ | </ | ||
| | XXX |< | | XXX |< | ||
openshift.1519209787.txt.gz · Last modified: (external edit)