Differences

This shows you the differences between two versions of the page.

--- openshift [2018/02/21 10:34] – [OpenShift CICD] skipidar
+++ openshift [2020/12/27 20:35] (current) – external edit 127.0.0.1
@@ Line 160: / Line 160: @@
   * Produces ready-to-run images by injecting application source into Docker image and assembling new Docker image
   * New image incorporates base image (builder) and built source and is ready to use with docker run command
+Reproducability. S2I supports incremental builds, which reuse previously downloaded dependencies, previously built artifacts, etc.
+Security. Builds and runs are executed as root, which may be exposed. S2I can execute commands with less rights.
+</WRAP>|
+| Image Stream |<WRAP>
+Docker images from different sources, identified by the same tag. \\
+Can be monitored, to trigger a build as a result.
+</WRAP>|
+| Jenkins pipeline |<WRAP>
+  * 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://developers.redhat.com/blog/wp-content/uploads/2016/12/FireShot-Capture-50-OpenShift-Web-Console_-https___192.168.123.1_8443_console-1024x174.png}}
+More:
+https://developers.redhat.com/blog/2017/01/09/using-pipelines-in-openshift-3-3-for-cicd/
+</WRAP>|
+| XXX |<WRAP>
+</WRAP>|
+| XXX |<WRAP>
+</WRAP>|
+| XXX |<WRAP>
 </WRAP>|
 | XXX |<WRAP>