This project uses the openshift-developer-tools scripts to manage its OpenShift Build and Deployment configurations. Refer to the associated project documentation for details.
templates/
frontend/
frontend-build.json // The Frontend builds to be added to tools project
frontend-deploy.json // Frontend deployment, to be added to application environments (dev, test, etc)
frontend-deploy-prod.json
nginx-runtime/
nginx-runtime-build.json // nginx-runtime build to be added to tools
yarn-builder/
yarn-builder-build.json // yarn-builder build to be added to tools
The project policies only need to be setup once.
Use initOSProjects.sh to setup the initial project policies on all of your projects at once.
The frontend-build.json defines a build configuration for a Jenkins Pipeline which uses the (jenkinsfile)[../Jenkinsfile] in the root of the repository. This file defines our declarative pipeline, currently this is how the pipeline is structured:
- Assemble Runtime and Builder images
- ⬇
- Build Application Artifacts
- Combine Artifacts with Runtime
- ⬇
- Tag the Image as
dev - Verify deployment in dev project
- Wait for approval ⏱
- ⬇
- Tag the Image as
test - Verify deployment in test project
- Wait for approval ⏱ to tag for prod
- ⬇
- Tag the Image as
prod
Use genParams.sh to setup your parameters for your various environments.
Use genBuilds.sh to publish or update your build configurations.
Use genDepls.sh to publish or update your deployment configurations.
Free OpenShift book from RedHat – good overview