When we started with Redhat’s OpenShift we were blown away by the 100s of possibilities to use it, while there was not anything along “This is how you make it work for your org”.
Its catalog provides items for almost everything - yet what we wanted is to enable people to quickly introduce Continous delivery and standardized technology archetypes. We call this lean, empowered governance.
So what does OpenDevStack now provide?
Trigger project creation thru the provisioning application to get a new project. The web GUI of the provisioning app is located at
openshiftproject == true, this will also create OpenShift projects, namely
A Jenkins deployment will be created in the
<project-KEY>-cd project to allow each project full freedom of build management. This deployment is based on common jenkins images from the
Open the web GUI of the provisioning app
This time, rather than
new initiative, pick
modify and select your project. Pick a matching quickstarter. If no framework fits to your needs, choose the
Now you got the boilerplate of the picked quickstarter in your BitBucket project in its own repository, which the provisioning app created. Also, CI/CD is already working - you can verify this as the boilerplate application runs in the
<project-KEY>-test project. This was deployed through a Jenkins pipeline, which is triggered via webhooks from BitBucket.
Create a branch in the newly created repository - once pushed this will deploy your application to the
<project-KEY>-dev project. After merging your branch to
master, the update is avilable in the
The branch-to-environment mapping is defined in the
Jenkinsfile, used by the jenkins shared library, and can be tailored to your needs.