This repository was archived by the owner on Mar 21, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
Trying out pull request changes in an OpenShift cluster
Michael Sauter edited this page Nov 9, 2023
·
5 revisions
For the remainder of this guide, we'll assume the branch you want to try out is named feature/some-new-functionality
, and ODS Pipeline is already installed in a namespace called foo-cd
. Adjust as necessary throughout.
Create a BuildConfig
resource for every image you need to build, that is start
, finish
and pipeline-manager
.
Example configuration for start
:
kind: BuildConfig
apiVersion: build.openshift.io/v1
metadata:
name: ods-start-preview
namespace: foo-cd
spec:
nodeSelector: null
output:
to:
kind: ImageStreamTag
name: 'start:latest'
resources: {}
successfulBuildsHistoryLimit: 5
failedBuildsHistoryLimit: 5
strategy:
type: Docker
dockerStrategy:
dockerfilePath: build/images/Dockerfile.start
postCommit: {}
source:
type: Git
git:
uri: 'https://github.com/opendevstack/ods-pipeline'
ref: feature/some-new-functionality
runPolicy: Serial
Also, for each build config, create an ImageStream
with corresponding name (for the example above, start
).
After all images have been created, run the install script from the deploy
directory like this:
./install.sh -n=foo-cd \
--local-chart \
--set imageRepository=image-registry.openshift-image-registry.svc:5000/foo-cd,imageTag=latest
Note: if ODS Pipeline has not been installed prior, you'll need to create a values.yaml
file before running this, as explained in the normal installation guide.