├── .github ├── ISSUE_TEMPLATE │ ├── bug_report.md │ └── feature_request.md └── PULL_REQUEST_TEMPLATE.md ├── .gitignore ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.adoc ├── Jenkinsfile ├── LICENSE ├── README.md ├── ansible.cfg ├── ci-playbook.yml ├── docs ├── run-with-docker.md └── run.sh ├── inventory ├── group_vars │ └── all.yml ├── host_vars │ ├── ci-cd-tooling.yml │ ├── ci-for-labs-ci-cd.yml │ └── projects-and-policies.yml └── hosts ├── meta └── main.yml ├── minimal-ci-install.yml ├── pre_post_requirements.yml ├── requirements.yml ├── site.yml └── whats-in-the-box.png /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Describe the bug** 11 | A clear and concise description of what the bug is. 12 | 13 | **To Reproduce** 14 | Steps to reproduce the behavior: 15 | 1. Go to '...' 16 | 2. Click on '....' 17 | 3. Scroll down to '....' 18 | 4. See error 19 | 20 | **Expected behavior** 21 | A clear and concise description of what you expected to happen. 22 | 23 | **Screenshots** 24 | If applicable, add screenshots to help explain your problem. 25 | 26 | **Desktop (please complete the following information):** 27 | - OS: [e.g. iOS] 28 | - Browser [e.g. chrome, safari] 29 | - Version [e.g. 22] 30 | 31 | **Smartphone (please complete the following information):** 32 | - Device: [e.g. iPhone6] 33 | - OS: [e.g. iOS8.1] 34 | - Browser [e.g. stock browser, safari] 35 | - Version [e.g. 22] 36 | 37 | **Additional context** 38 | Add any other context about the problem here. 39 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Is your feature request related to a problem? Please describe.** 11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] 12 | 13 | **Describe the solution you'd like** 14 | A clear and concise description of what you want to happen. 15 | 16 | **Describe alternatives you've considered** 17 | A clear and concise description of any alternative solutions or features you've considered. 18 | 19 | **Additional context** 20 | Add any other context or screenshots about the feature request here. 21 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | #### What is this PR About? 2 | 3 | Brief explanation of the guide or document changes you have made and/or 4 | the new content you are contributing. 5 | 6 | #### How should we test or review this PR? 7 | 8 | Include any information or commands (please use code blocks) to help 9 | reviewers understand and verify your contribution. 10 | 11 | #### Is there a relevant Trello card or Github issue open for this? 12 | 13 | Provide a link to any open Github issues or Trello cards that describe 14 | the use case or problem you are solving. 15 | 16 | #### Who would you like to review this? 17 | 18 | cc: @rht-labs/OpenInnovationLabs 19 | 20 | ''''' 21 | 22 | * [ ] Have you followed the 23 | [contributing 24 | guidelines?](https://github.com/rht-labs/labs-ci-cd/blob/master/CONTRIBUTING.adoc) 25 | * [ ] Have you explained what your changes do, and why they add value to 26 | Labs CI / CD? 27 | 28 | ''''' 29 | 30 | *Please note: we may close your PR without comment if you do not check 31 | the boxes above and provide ALL requested information.* 32 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | openshift-applier 2 | roles/* 3 | *.pyc 4 | .idea 5 | *.iml 6 | gdsl 7 | *.retry 8 | *.swp 9 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as 6 | contributors and maintainers pledge to making participation in our 7 | project and our community a harassment-free experience for everyone, 8 | regardless of age, body size, disability, ethnicity, gender identity and 9 | expression, level of experience, nationality, personal appearance, race, 10 | religion, or sexual identity and orientation. 11 | 12 | ## Our Standards 13 | 14 | Examples of behavior that contributes to creating a positive environment 15 | include: 16 | 17 | * Using welcoming and inclusive language 18 | * Being respectful of differing viewpoints and experiences 19 | * Gracefully accepting constructive criticism 20 | * Focusing on what is best for the community 21 | * Showing empathy towards other community members 22 | 23 | Examples of unacceptable behavior by participants include: 24 | 25 | * The use of sexualized language or imagery and unwelcome sexual 26 | attention or advances 27 | * Trolling, insulting/derogatory comments, and personal or political 28 | attacks 29 | * Public or private harassment 30 | * Publishing others’ private information, such as a physical or 31 | electronic address, without explicit permission 32 | * Other conduct which could reasonably be considered inappropriate in a 33 | professional setting 34 | 35 | ## Our Responsibilities 36 | 37 | Project maintainers are responsible for clarifying the standards of 38 | acceptable behavior and are expected to take appropriate and fair 39 | corrective action in response to any instances of unacceptable behavior. 40 | 41 | Project maintainers have the right and responsibility to remove, edit, 42 | or reject comments, commits, code, wiki edits, issues, and other 43 | contributions that are not aligned to this Code of Conduct, or to ban 44 | temporarily or permanently any contributor for other behaviors that they 45 | deem inappropriate, threatening, offensive, or harmful. 46 | 47 | ## Scope 48 | 49 | This Code of Conduct applies both within project spaces and in public 50 | spaces when an individual is representing the project or its community. 51 | Examples of representing a project or community include using an 52 | official project e-mail address, posting via an official social media 53 | account, or acting as an appointed representative at an online or 54 | offline event. Representation of a project may be further defined and 55 | clarified by project maintainers. 56 | 57 | ## Enforcement 58 | 59 | Instances of abusive, harassing, or otherwise unacceptable behavior may 60 | be reported by contacting the project team at hello-labs@redhat.com. 61 | All complaints will be reviewed and investigated and will result in a 62 | response that is deemed necessary and appropriate to the circumstances. 63 | The project team is obligated to maintain confidentiality with regard to 64 | the reporter of an incident. Further details of specific enforcement 65 | policies may be posted separately. 66 | 67 | Project maintainers who do not follow or enforce the Code of Conduct in 68 | good faith may face temporary or permanent repercussions as determined 69 | by other members of the project’s leadership. 70 | 71 | ## Attribution 72 | 73 | This Code of Conduct is adapted from the 74 | https://www.contributor-covenant.org[Contributor Covenant], version 1.4, 75 | available at 76 | https://www.contributor-covenant.org/version/1/4/code-of-conduct.html 77 | -------------------------------------------------------------------------------- /CONTRIBUTING.adoc: -------------------------------------------------------------------------------- 1 | = Contributing to Labs CI / CD 2 | :toc: 3 | :toc-title: 4 | :toc-placement!: 5 | 6 | Thanks for checking out the Labs CI / CD guides! We’re excited to hear 7 | and learn from you. Your experiences will benefit others who read and 8 | use these guides. 9 | 10 | We’ve put together the following guidelines to help you figure out where 11 | you can best be helpful. 12 | 13 | toc::[] 14 | 15 | == Types of contributions we’re looking for 16 | 17 | This project is used as a starting point for CI/CD tooling by the 18 | Red Hat Open Innovation Labs group. It incoporates many technologies 19 | and is intended for development on OpenShift Container Platform. 20 | 21 | Interested in making a contribution? Read on! 22 | 23 | == Ground rules & expectations 24 | 25 | Before we get started, here are a few things we expect from you (and 26 | that you should expect from others): 27 | 28 | * Be kind and thoughtful in your conversations around this project. We 29 | all come from different backgrounds and projects, which means we likely 30 | have different perspectives on "how open source is done". Try to 31 | listen to others rather than convince them that your way is correct. 32 | * There is a 33 | link:./CODE_OF_CONDUCT.md[Contributor Code of Conduct]. By participating 34 | in this project, you agree to abide by its terms. 35 | * If you open a pull request, please ensure that your contribution 36 | passes all tests. If there are test failures, you will need to address 37 | them before we can merge your contribution. 38 | 39 | == Getting set up for local development 40 | 41 | Local Development guide is still under construction... 42 | 43 | === Deploying to OpenShift 44 | 45 | The Labs CI / CD stack can be deployed to any OpenShift cluster, and is automated using link:https://github.com/redhat-cop/openshift-applier[OpenShift Applier]. The following commands can be used to install Applier, log in to your OpenShift cluster, and deploy the pipeline. 46 | 47 | [source,bash] 48 | ---- 49 | ansible-galaxy install -r requirements.yml -p roles 50 | oc login ... 51 | ansible-playbook roles/openshift-applier/playbooks/openshift-cluster-seed.yml 52 | ---- 53 | 54 | This will result in the creation of several tools and environments across several projects: 55 | 56 | * `labs-ci-cd` is where Jenkins, and other tools will be deployed to. 57 | * `labs-dev` will be used as the Development environment, where smoke tests can be run. 58 | * `labs-test` is a promotion environment 59 | 60 | If you need to customize the deployment (e.g. for testing a Pull Request), the Applier inventory supports a number of parameters to customize the deployment. The following command is an example of configuring the pipeline to build from an alternative fork and branch. For other possible parameters, see link:inventory/group_vars/all.yml[all.yml]. 61 | 62 | == Contributing Content 63 | 64 | If you’d like to contribute, start by searching through the GitHub 65 | https://github.com/rht-labs/labs-ci-cd/issues[issues] and 66 | https://github.com/rht-labs/labs-ci-cd/pulls[pull requests] to see 67 | whether someone else has raised a similar idea or question. 68 | 69 | If you don’t see your idea listed, and you think it fits into the goals 70 | of this guide, do one of the following: * *If your contribution is 71 | minor,* such as a typo fix, open a pull request. * *If your contribution 72 | is major,* such as a new article or category, start by opening an issue 73 | first. That way, other people can weigh in on the discussion before you 74 | do any work. 75 | 76 | == Contribution review process 77 | 78 | This repo is currently maintained by @springdo, @pcarney8, @mcanoy, and 79 | @oybed, who have commit access. They will likely review your 80 | contribution. If you haven’t heard from anyone in 10 days, feel free to 81 | bump the thread or @-mention a maintainer or 82 | `@rht-labs/OpenInnovationLabs` to review your contribution. 83 | 84 | == Community 85 | 86 | Discussions about Labs CI / CD takes place within this repository’s 87 | https://github.com/rht-labs/labs-ci-cd/issues[Issues] and 88 | https://github.com/rht-labs/labs-ci-cd/pulls[Pull Requests] 89 | sections. 90 | 91 | Wherever possible, do not take these conversations to private channels, 92 | including contacting the maintainers directly. Keeping communication 93 | public means everybody can benefit and learn from the conversation. 94 | -------------------------------------------------------------------------------- /Jenkinsfile: -------------------------------------------------------------------------------- 1 | @NonCPS 2 | def notifyGitHub(state) { 3 | sh "curl -u ${env.USER_PASS} -d '${state}' -H 'Content-Type: application/json' -X POST ${env.PR_STATUS_URI}" 4 | } 5 | 6 | def getGitHubPullRequest() { 7 | def output = sh(returnStdout: true, script: "curl -u ${env.USER_PASS} -H 'Content-Type: application/json' -X GET ${env.PR_URI}") 8 | 9 | def json = readJSON text: output 10 | 11 | return json 12 | } 13 | 14 | def clearProjects(){ 15 | sh """ 16 | oc delete project $PR_CI_CD_PROJECT_NAME || rc=\$? 17 | oc delete project $PR_DEV_PROJECT_NAME || rc=\$? 18 | oc delete project $PR_TEST_PROJECT_NAME || rc=\$? 19 | while \${unfinished} 20 | do 21 | oc get project $PR_CI_CD_PROJECT_NAME || \ 22 | oc get project $PR_DEV_PROJECT_NAME || \ 23 | oc get project $PR_TEST_PROJECT_NAME || unfinished=false 24 | done 25 | """ 26 | } 27 | 28 | 29 | pipeline { 30 | 31 | agent { 32 | label "master" 33 | } 34 | 35 | environment { 36 | // Global Vars 37 | JOB_NAME = "${JOB_NAME}".replace("/", "-") 38 | GIT_SSL_NO_VERIFY = true 39 | URL_TO_TEST = "https://google.com" 40 | PR_GITHUB_USERNAME = "labs-robot" 41 | 42 | } 43 | 44 | // The options directive is for configuration that applies to the whole job. 45 | options { 46 | buildDiscarder(logRotator(numToKeepStr:'10')) 47 | timeout(time: 35, unit: 'MINUTES') 48 | // ansiColor('xterm') 49 | // timestamps() 50 | } 51 | 52 | stages { 53 | stage("Prepare Environment") { 54 | agent { 55 | node { 56 | label "master" 57 | } 58 | } 59 | steps { 60 | echo "Setting up environment variables" 61 | script { 62 | env.OCP_API_SERVER = "${env.OPENSHIFT_API_URL}" 63 | env.OCP_TOKEN = readFile('/var/run/secrets/kubernetes.io/serviceaccount/token').trim() 64 | 65 | // Get the PR ID 66 | timeout(time: 1, unit: 'HOURS') { 67 | env.PR_ID = input( 68 | id: 'userInput', message: 'Which PR # do you want to test?', parameters: [ 69 | [$class: 'StringParameterDefinition', description: 'PR #', name: 'pr'] 70 | ]) 71 | if (env.PR_ID == null || env.PR_ID == ""){ 72 | error('PR_ID cannot be null or empty') 73 | } 74 | } 75 | 76 | env.PR_CI_CD_PROJECT_NAME = "labs-ci-cd-pr-${env.PR_ID}" 77 | env.PR_DEV_PROJECT_NAME = "labs-dev-pr-${env.PR_ID}" 78 | env.PR_TEST_PROJECT_NAME = "labs-test-pr-${env.PR_ID}" 79 | 80 | env.PR_GITHUB_TOKEN = new String("oc get secret labs-robot-github-oauth-token --template='{{.data.password}}'".execute().text.minus("'").minus("'").decodeBase64()) 81 | if (env.PR_GITHUB_TOKEN == null || env.PR_GITHUB_TOKEN == ""){ 82 | error('PR_GITHUB_TOKEN cannot be null or empty') 83 | } 84 | env.USER_PASS = "${env.PR_GITHUB_USERNAME}:${env.PR_GITHUB_TOKEN}" 85 | 86 | env.PR_BRANCH = "pull/${env.PR_ID}/head" 87 | env.PR_URI = "https://api.github.com/repos/rht-labs/labs-ci-cd/pulls/${env.PR_ID}" 88 | env.PR_STATUS_URI = getGitHubPullRequest().statuses_url 89 | 90 | echo env.PR_STATUS_URI 91 | } 92 | } 93 | } 94 | 95 | stage("Clear Existing Projects") { 96 | steps { 97 | echo "Removing old PR projects if they exist to ensure a clean slate to test against" 98 | clearProjects() 99 | } 100 | } 101 | 102 | // Uses sequential stages so same slave / workspace is preserved i.e. no need for stash link: https://jenkins.io/blog/2018/07/02/whats-new-declarative-piepline-13x-sequential-stages/ 103 | stage ("Spin up shared ansible slave") { 104 | agent { 105 | node { 106 | label "jenkins-slave-ansible" 107 | } 108 | } 109 | when { 110 | expression { return env.PR_ID } 111 | } 112 | stages { 113 | stage("Merge PR") { 114 | 115 | steps { 116 | echo "Pushing build state to the PR" 117 | 118 | notifyGitHub('''{ 119 | "state": "pending", 120 | "description": "ALL CI jobs are running...", 121 | "context": "Jenkins" 122 | }''') 123 | 124 | sh """ 125 | git config --global user.email "labs.robot@gmail.com" 126 | git config --global user.name "Labs Robot" 127 | git checkout master 128 | git fetch origin ${env.PR_BRANCH}:pr 129 | git merge pr --ff 130 | """ 131 | } 132 | } 133 | 134 | stage("Apply ci-for-ci Inventory") { 135 | steps { 136 | echo "Applying inventory" 137 | // each its own line to that in blue ocean UI they show seperately 138 | sh "ansible-galaxy install -r requirements.yml --roles-path=roles" 139 | sh "ansible-playbook site.yml -e ci_cd_namespace=${env.PR_CI_CD_PROJECT_NAME} -e dev_namespace=${env.PR_DEV_PROJECT_NAME} -e test_namespace=${env.PR_TEST_PROJECT_NAME} -e role=admin" 140 | 141 | } 142 | // Post can be used both on individual stages and for the entire build. 143 | post { 144 | success { 145 | notifyGitHub('''{ 146 | "state": "success", 147 | "description": "job completed :)", 148 | "context": "Apply Inventory" 149 | }''') 150 | } 151 | failure { 152 | notifyGitHub('''{ 153 | "state": "failure", 154 | "description": "job failed :(", 155 | "context": "Apply Inventory" 156 | }''') 157 | } 158 | } 159 | } 160 | } 161 | } 162 | 163 | stage("Verifying CI Builds") { 164 | steps { 165 | notifyGitHub('''{ 166 | "state": "pending", 167 | "description": " job is running...", 168 | "context": "CI Builds" 169 | }''') 170 | 171 | node('master') { 172 | echo "Verifying the CI Builds have completed successfully" 173 | script { 174 | openshift.withCluster() { 175 | openshift.withProject("${env.PR_CI_CD_PROJECT_NAME}") { 176 | timeout(5) { 177 | def pipelineBuildConfigs = openshift.selector('bc', [ type:'pipeline']) 178 | def imageBuildConfigs = openshift.selector('bc', [ type:'image']) 179 | def allDone = true 180 | imageBuildConfigs.withEach { 181 | echo "CI Builds: Checking ${it.name()}" 182 | def imageBuildName = it.name() 183 | def isPipelineBuild = false 184 | pipelineBuildConfigs.withEach { 185 | if (it.name() == imageBuildName) { 186 | isPipelineBuild = true 187 | } 188 | } 189 | 190 | if (isPipelineBuild == false) { 191 | if (it.object().status.phase != "Complete") { 192 | allDone = false 193 | } 194 | } 195 | } 196 | return allDone; 197 | } 198 | } 199 | } 200 | } 201 | } 202 | } 203 | // Post can be used both on individual stages and for the entire build. 204 | post { 205 | success { 206 | notifyGitHub('''{ 207 | "state": "success", 208 | "description": "job completed :)", 209 | "context": "CI Builds" 210 | }''') 211 | } 212 | failure { 213 | notifyGitHub('''{ 214 | "state": "failure", 215 | "description": "job failed :(", 216 | "context": "CI Builds" 217 | }''') 218 | } 219 | } 220 | } 221 | 222 | stage("Verifying CI Deploys") { 223 | steps { 224 | notifyGitHub('''{ 225 | "state": "pending", 226 | "description": " job is running...", 227 | "context": "CI Deploys" 228 | }''') 229 | 230 | node('master') { 231 | echo "Verifying the CI Deploys have completed successfully" 232 | script { 233 | openshift.withCluster() { 234 | openshift.withProject("${env.PR_CI_CD_PROJECT_NAME}") { 235 | timeout(10) { 236 | def deploymentConfigs = openshift.selector('dc') 237 | deploymentConfigs.withEach { 238 | echo "Checking ${env.PR_CI_CD_PROJECT_NAME}:${it.name()}" 239 | // this will wait until the desired replicas are available 240 | // - or be terminated at timeout 241 | it.rollout().status() 242 | } 243 | } 244 | } 245 | } 246 | } 247 | } 248 | } 249 | // Post can be used both on individual stages and for the entire build. 250 | post { 251 | success { 252 | notifyGitHub('''{ 253 | "state": "success", 254 | "description": "job completed :)", 255 | "context": "CI Deploys" 256 | }''') 257 | } 258 | failure { 259 | notifyGitHub('''{ 260 | "state": "failure", 261 | "description": "job failed :(", 262 | "context": "CI Deploys" 263 | }''') 264 | } 265 | } 266 | } 267 | 268 | stage("Clear Existing Projects on Successful Job") { 269 | steps { 270 | echo "Removing old PR projects if they exist to ensure a clean slate to test against" 271 | clearProjects() 272 | } 273 | } 274 | 275 | } 276 | // global post hook 277 | post { 278 | success { 279 | notifyGitHub('''{ 280 | "state": "success", 281 | "description": "master ci job completed :)", 282 | "context": "Jenkins" 283 | }''') 284 | } 285 | failure { 286 | notifyGitHub('''{ 287 | "state": "failure", 288 | "description": "master ci job failed :(", 289 | "context": "Jenkins" 290 | }''') 291 | } 292 | } 293 | } 294 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "{}" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright {yyyy} {name of copyright owner} 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Open Innovation Labs CI/CD 2 | 3 | ## 🏁 No Longer Being Maintained 🌇 4 | This project is being deprecated and will no longer receive updates or contributions. OpenShift has moved on to version 4.x and this project was a great enabler for kick starting development of applications on OpenShift 3.x. The tools of DevOps have evolved and grown towards a GitOps approach and so the evolution of Labs CI/CD has moved that way too. 5 | 6 | For this teams new approach to tooling and automation checkout these two repositories: 7 | - 🐙 [The new home for labs ci cd and other tooling](https://github.com/rht-labs/ubiquitous-journey) 🐙 8 | - ⚓️ [Our custom Helm Charts](https://github.com/rht-labs/helm-charts) ⚓️ 9 | 10 | ## What's in the box? 11 | 12 | This project is an Ansible inventory for loading an OpenShift cluster with some frequently used projects, apps and tools on a Red Hat Open Innovation Lab residencies. Using the `openshift-applier`, cluster content is loaded from templates and param files in a repeatable, config-as-code way. 13 | 14 | Running this Ansible inventory will first create three project namespaces: `labs-ci-cd`, `labs-dev` and `labs-test`. Subsequently it will create a bunch of commonly used `ci-cd-tools` such as Jenkins, Nexus and Sonar. It will also create a collection of `jenkins-slaves` that can be used in builds such as `npm`, `maven` and `golang` to name a few. Apps can be added also by applying their `Jenkinsfile` as a buildConfig with an example (java-app) is included as a reference. 15 | 16 | The diagaram below shows the components that get created by running the playbook's `bootstrap` and `tools` inventories. 17 | ![whats-in-the-box.png](whats-in-the-box.png) 18 | 19 | ## How it Works 20 | The layout of the project is like most standard `ansible-playbooks` with a simplified view of the key parts shown below: 21 | ```bash 22 | . 23 | ├── site.yml 24 | ├── requirements.yml 25 | ├── inventory 26 | │   ├── group_vars 27 | │   │   └── all.yml 28 | │   ├── host_vars 29 | │   | └── ... 30 | │   └── hosts 31 | ├── params 32 | │   └── jenkins-slaves 33 | │   └── ** 34 | ├── secrets 35 | │   └── ... 36 | ``` 37 | * `site.yml` is a playbook that sets up some variables and drives the `openshift-applier` role. 38 | * `requirements.yml` is a manifest which contains the Ansible modules needed to run the playbook 39 | * `inventory/host_vars/*.yml` is the collection of objects we want to insert into the cluster written according to [the convention defined by the openshift-applier role](https://github.com/redhat-cop/openshift-applier/tree/master/roles/openshift-applier#sourcing-openshift-object-definitions). 40 | * `inventory/hosts` is where the `targets` are defined for grouping of the various inventories to be run eg `bootsrap` for creating projects and roles bindings 41 | * `params` is a set of [parameter files](https://docs.openshift.com/container-platform/;latest/dev_guide/templates.html#templates-parameters) to be processed along with their respective OpenShift template. The convention here is to group files by their application. 42 | 43 | ### Multiple inventories 44 | The Ansible layer is very thin; it simply provides a way to orchestrate the application of [OpenShift templates](https://docs.openshift.com/container-platform/latest/dev_guide/templates.html) across one or more [OpenShift projects](https://docs.openshift.com/container-platform/latest/architecture/core_concepts/projects_and_users.html#projects). All configuration for the applications should be defined by an OpenShift template and the corresponding parameters file. 45 | 46 | There are multiple Ansible inventories which divide the type of components to be built and deployed to an OpenShift cluster. These are broken down into three sections: 47 | * `bootstrap` - Located in `inventory/host_vars/projects-and-policies.yml` contains a collection of objects used to create project namespaces and bind roles to groups for those namespace in OpenShift 48 | * `tools` - Located in `inventory/host_vars/ci-cd-tooling.yml` contains the collection of Jenkins slaves, Jenkins S2I and other CI/CD tooling deployments such as SonarQube, Nexus and others. 49 | * `apps` - Located in `inventory/host_vars/app-build-deploy.yml` contains definitions for the Java reference app's build and deploy 50 | 51 | 52 | ## Getting Started 53 | 54 | ### Prerequisites 55 | 56 | * [Ansible](http://docs.ansible.com/ansible/latest/intro_installation.html) 2.5 or above. 57 | * [OpenShift CLI Tools](https://docs.openshift.com/container-platform/latest/cli_reference/get_started_cli.html) 58 | * Access to the OpenShift cluster (Your user needs permissions to deploy ProjectRequest objects) 59 | * libselinux-python (only needed on Fedora, RHEL, and CentOS) 60 | - Install by running `yum install libselinux-python`. 61 | 62 | ### Inventory Usage 63 | It should be noted that non-docker executions will utilize the inventory directory included in this repo by default. If you would like to specify a custom inventory for any of the below tasks, you can do so by adding `-i /path/to/my/inventory` to the command 64 | 65 | ### Basic Usage 66 | 67 | 1. Log on to an OpenShift server `oc login -u https://:/` 68 | 2. Clone this repository. 69 | 3. Install the required [openshift-applier](https://github.com/redhat-cop/openshift-applier) dependency: 70 | ```bash 71 | ansible-galaxy install -r requirements.yml --roles-path=roles 72 | ``` 73 | 4. To deploy everything please run: 74 | ```bash 75 | ansible-playbook site.yml 76 | ``` 77 | 78 | ## Customised Install 79 | 80 | If `labs-ci-cd` already exists on your OpenShift cluster and you want to create a new instance of `labs-ci-cd` with its own name eg `john-ci-cd`, run the "unique projects" playbook. This playbook is useful if you're developing labs-ci-cd and want to test your changes. With a unique project name, you can safely try out your changes in a test cluster that others are using. 81 | 82 | ```bash 83 | ansible-playbook site.yml -e ci_cd_namespace=another-ci-cd -e dev_namespace=another-dev -e test_namespace=another-test 84 | ``` 85 | 86 | Or please look [here](inventory/group_vars/all.yml) for other variables you can change. 87 | 88 | Note: 89 | - Only numbers, lowercase letters, and dashes are allowed in project names. 90 | 91 | After running the playbook, the pipeline should execute in Jenkins, build the spring boot app, deploy artifacts to nexus, deploy the container to the dev stage and then wait approval to deploy to the demo stage. See Common Issues 92 | 93 | ## Persistent vs Ephemeral Jenkins 94 | 95 | `labs-ci-cd` will default to deploying a persistent Jenkins, if you do not wish to use persistent jenkins please add on the extra variable `jenkins_persistence_type` and set it to `ephemeral` For Example: 96 | 97 | ```bash 98 | ansible-playbook site.yml -e jenkins_persistence_type=ephemeral 99 | ``` 100 | 101 | ## Running a Subset of the Inventory 102 | 103 | In some cases you might not want to deploy all of the components in this repo; but only a subset such as Jenkins and the customisations to it. 104 | 105 | 1. See [the docs](https://github.com/redhat-cop/openshift-applier/tree/master/roles/openshift-applier#filtering-content-based-on-tags) in the openshift-applier repo. 106 | 2. The only required tag to deploy objects within the inventory is **projects**, all other tags are *optional* 107 | 3. Here is an example that runs the tags that provision projects, ci, and jenkins objects: 108 | ```bash 109 | ansible-playbook site.yml \ 110 | -e "include_tags=jenkins,ci,projects" 111 | ``` 112 | 113 | ## Scope and Direction 114 | 115 | The goal of this repository is to: 116 | 117 | 1. Bootstrap Labs residencies will all the tools necessary for a comprehensive, OpenShift native CI/CD pipeline 118 | 2. Serve as a reference implementation of the [openshift-applier](https://github.com/redhat-cop/openshift-applier/tree/master/roles/openshift-applier) model for Infrastructure-as-Code (IaC) 119 | 120 | A few additional guiding principles: 121 | 122 | * This repository is built to ensure all the individual components are integrated and can be deployed together. 123 | * It is likely that your residency will need to remove some components in this inventory and then add others. Thus, every residency team is encouraged to create a fork of this repo and modify to their needs. A few things to consider for your fork: 124 | - Avoid using local Templates in this repo, Templates should always point to a *tag* of [redhat-cop/containers-quickstarts](https://github.com/redhat-cop/containers-quickstarts) or [rht-labs/openshift-templates](https://github.com/rht-labs/openshift-templates). This encourages reuse, as well as contributions back to the upstream effort. 125 | - If you build new, reusable features in your fork, contribute them back! 126 | * Generally speaking, there should only be one tool per functional use case e.g. Sonatype Nexus is the artifact repository so we will not support JFrog Artifactory 127 | 128 | ## Contributing 129 | 130 | 1) Fork the repo and open PR's 131 | 2) Add all new components to the inventory with appropriate namespaces and tags 132 | 3) Extended the `Jenkinsfile` with steps to verify that your components built/deployed correctly 133 | 4) For now, it is your responsibility to run the CI job. Please contact an admin for the details to set the CI job up. 134 | 5) The `tests/slaves/Jenkinsfile` gets run as part of CI and will spin up a new Jenkins instance from this repositories code and validate each of the provided slaves can be accessed and contain their expected binary on the path. 135 | 136 | ## Common Issues 137 | 138 | * Issues with valid nexus certs like seen [here](https://github.com/redhat-cop/infra-ansible/issues/342). You can set the ansible variable `nexus_validate_certs: false` as a work around. 139 | * S2I Build fails to push image to registry with `error: build error: Failed to push image: unauthorized: authentication required`. See [this issue](https://github.com/openshift/origin/issues/4518) 140 | 141 | 142 | ## License 143 | [ASL 2.0](LICENSE) 144 | -------------------------------------------------------------------------------- /ansible.cfg: -------------------------------------------------------------------------------- 1 | [defaults] 2 | inventory=inventory 3 | -------------------------------------------------------------------------------- /ci-playbook.yml: -------------------------------------------------------------------------------- 1 | --- 2 | - name: Setting up CI for Labs CI/CD 3 | hosts: "ci-for-labs" 4 | roles: 5 | - openshift-applier/roles/openshift-applier -------------------------------------------------------------------------------- /docs/run-with-docker.md: -------------------------------------------------------------------------------- 1 | ## Getting Started With Docker 2 | 3 | There are two ways to use Labs CI/CD. The preferred approach is to run the playbook using a docker container. This ensures consistency of the execution environment for all users. If you have the prerequisites installed feel free to read the [Getting Started Without Docker section](#getting-started-without-docker). 4 | 5 | ### Prerequisites 6 | 7 | * [Docker CE](https://www.docker.com/community-edition#/download) 8 | * [OpenShift CLI Tools](https://docs.openshift.com/container-platform/latest/cli_reference/get_started_cli.html) 9 | * Access to the OpenShift cluster (Your user needs permissions to deploy ProjectRequest objects) 10 | 11 | ### Usage 12 | 13 | 1. Log on to an OpenShift server `oc login -u https://:/` 14 | 2. Clone this repository. 15 | 3. If `labs-ci-cd` doesn't yet exist on your OpenShift cluster, just run the default `run.sh` script: 16 | ```bash 17 | ./run.sh 18 | ``` 19 | 20 | ## Customised Install 21 | 22 | If `labs-ci-cd` already exists on your OpenShift cluster and you want to create a new instance of `labs-ci-cd` with its own name eg `john-ci-cd`, run the "unique projects" playbook. This playbook is useful if you're developing labs-ci-cd and want to test your changes. With a unique project name, you can safely try out your changes in a test cluster that others are using. 23 | 24 | ```bash 25 | ./run.sh ansible-playbook /tmp/src/unique-projects-playbook.yml \ 26 | -i /tmp/src/inventory/ \ 27 | -e ci_cd_namespace=another-ci-cd \ 28 | -e dev_namespace=another-dev \ 29 | -e test_namespace=another-test 30 | ``` 31 | 32 | ## Running a Subset of the Inventory 33 | 34 | In some cases you might not want to deploy all of the components in this repo; but only a subset such as Jenkins and the customisations to it. 35 | 36 | 1. See [the docs](https://github.com/redhat-cop/openshift-applier/tree/master/roles/openshift-applier#filtering-content-based-on-tags) in the openshift-applier repo. 37 | 2. The only required tag to deploy objects within the inventory is **projects**, all other tags are *optional* 38 | 3. If using `./run.sh` and docker, here is an example that runs the tags that provision projects, ci, and jenkins objects: 39 | ```bash 40 | ./run.sh ansible-playbook /tmp/src/apply.yml \ 41 | -i /tmp/src/inventory/ \ 42 | -e target=tools \ 43 | -e "include_tags=jenkins,ci,projects" 44 | ``` -------------------------------------------------------------------------------- /docs/run.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | ###################################################################################### 4 | # 5 | # The objective of this script is to: 6 | # 1) make the docker run command easier to use. 7 | # 2) run ansible-galaxy install if required roles are missing. 8 | # 3) print ASCII art. 9 | # 10 | # Please do not introduce any other logic 11 | # 12 | ###################################################################################### 13 | set -e 14 | 15 | function printBanner(){ 16 | # fpr info on colors, see https://stackoverflow.com/questions/5947742/how-to-change-the-output-color-of-echo-in-linux 17 | LIGHT_BLUE='\033[1;34m' 18 | GREEN='\033[0;32m' 19 | RED='\033[0;31m' 20 | WHITE='\033[1;37m' 21 | NC='\033[0m' 22 | 23 | printf " 24 | ${RED} _ _ ${LIGHT_BLUE} ____ ___ ${WHITE} __${GREEN} ____ ____ \n\ 25 | ${RED}| | __ _| |__ ___ ${LIGHT_BLUE} / ___|_ _|${WHITE} / /${GREEN}/ ___| _ \ \n\ 26 | ${RED}| | / _' | ' \/ __| ${LIGHT_BLUE}| | | | ${WHITE} / /${GREEN}| | | | | | \n\ 27 | ${RED}| |__| (_| | |_) \__ \ ${LIGHT_BLUE}| |___ | | ${WHITE} / / ${GREEN}| |___| |_| | \n\ 28 | ${RED}|_____\__,_|_.__/|___/ ${LIGHT_BLUE} \____|___|${WHITE}/_/ ${GREEN} \____|____/ \n\ 29 | \n\n${NC}" 30 | } 31 | 32 | ########################### 33 | # Begin Script # 34 | ########################### 35 | printBanner 36 | 37 | if [[ "$#" == 0 ]]; then 38 | DOCKER_RUN_COMMAND='ansible-playbook -i /tmp/src/inventory /tmp/src/apply.yml -e target=bootstrap && ansible-playbook -i /tmp/src/inventory /tmp/src/apply.yml -e target=tools' 39 | printf "no arguments passed to run.sh. using default docker run command:\n- $DOCKER_RUN_COMMAND\n\n" 40 | else 41 | DOCKER_RUN_COMMAND="$@" 42 | printf "using arguments passed to run.sh for docker run command:\n\t$DOCKER_RUN_COMMAND\n\n" 43 | 44 | fi 45 | 46 | DOCKER_RUN_COMMAND="ansible-galaxy install -r /tmp/src/requirements.yml --roles-path=/tmp/src/roles && $DOCKER_RUN_COMMAND" 47 | 48 | docker run --rm -i \ 49 | -v $(pwd):/tmp/src:z \ 50 | -v $HOME/.kube:/root/.kube:z \ 51 | -t quay.io/redhat-cop/openshift-applier:v2.0.6 \ 52 | /bin/sh -c "$DOCKER_RUN_COMMAND" 53 | 54 | 55 | -------------------------------------------------------------------------------- /inventory/group_vars/all.yml: -------------------------------------------------------------------------------- 1 | ci_cd_namespace: labs-ci-cd 2 | dev_namespace: labs-dev 3 | test_namespace: labs-test 4 | 5 | openshift_templates_raw: "https://raw.githubusercontent.com/redhat-cop/openshift-templates" 6 | openshift_templates_raw_version_tag: "v1.4.12" 7 | cop_quickstarts: "https://github.com/redhat-cop/containers-quickstarts.git" 8 | cop_quickstarts_raw: "https://raw.githubusercontent.com/redhat-cop/containers-quickstarts" 9 | cop_quickstarts_raw_version_tag: "v1.18" 10 | 11 | ci_cd: 12 | NAMESPACE: "{{ ci_cd_namespace }}" 13 | NAMESPACE_DISPLAY_NAME: "{{ ci_cd_namespace }}" 14 | SECRET_NAME: "ci-cd-secret" 15 | 16 | dev: 17 | NAMESPACE: "{{ dev_namespace }}" 18 | NAMESPACE_DISPLAY_NAME: "{{ dev_namespace }}" 19 | 20 | test: 21 | NAMESPACE: "{{ test_namespace }}" 22 | NAMESPACE_DISPLAY_NAME: "{{ test_namespace }}" 23 | 24 | edit_role_binding_group: 25 | GROUP: "labs-ci-cd-contributors" 26 | ROLE: "{{ role | default('edit') }}" 27 | admin_role_binding_group: 28 | GROUP: "ocp-devs" 29 | ROLE: "admin" 30 | -------------------------------------------------------------------------------- /inventory/host_vars/ci-cd-tooling.yml: -------------------------------------------------------------------------------- 1 | --- 2 | ansible_connection: local 3 | 4 | jenkins_name: jenkins 5 | sonarqube_name: sonarqube 6 | hoverfly_name: hoverfly 7 | nexus_password: "admin123" 8 | 9 | jenkins_persistence_type: "persistent" 10 | 11 | jenkins: 12 | build: 13 | NAME: "{{ jenkins_name }}" 14 | SOURCE_REPOSITORY_URL: https://github.com/rht-labs/s2i-config-jenkins.git 15 | SOURCE_REPOSITORY_REF: v1.5 16 | IMAGE_STREAM_NAMESPACE: "{{ ci_cd_namespace }}" 17 | SECRET_NAME: "jenkins-git-password" 18 | USERNAME: gitlab-sa 19 | PASSWORD: "some-secret-password" 20 | SOURCE_REPOSITORY_SECRET: "jenkins-git-password" 21 | deploy: 22 | NAMESPACE: "{{ ci_cd_namespace }}" 23 | JENKINS_IMAGE_STREAM_TAG: "{{ jenkins_name }}:latest" 24 | MEMORY_LIMIT: 6Gi 25 | JENKINS_OPTS: "--sessionTimeout=720" 26 | VOLUME_CAPACITY: 20Gi 27 | MEMORY_REQUEST: 2Gi 28 | JVM_ARCH: x86_64 29 | GITLAB_HOST: "gitlab.mydomain.example.com" 30 | GITLAB_TOKEN: "token123" 31 | GITLAB_GROUP_NAME: "rht-labs" 32 | 33 | jenkins_slaves: 34 | build: 35 | ansible: 36 | NAME: jenkins-slave-ansible 37 | SOURCE_CONTEXT_DIR: jenkins-slaves/jenkins-slave-ansible 38 | SOURCE_REPOSITORY_REF: "{{ cop_quickstarts_raw_version_tag }}" 39 | SOURCE_REPOSITORY_URL: "{{ cop_quickstarts }}" 40 | arachni: 41 | NAME: jenkins-slave-arachni 42 | SOURCE_CONTEXT_DIR: jenkins-slaves/jenkins-slave-arachni 43 | SOURCE_REPOSITORY_REF: "{{ cop_quickstarts_raw_version_tag }}" 44 | SOURCE_REPOSITORY_URL: "{{ cop_quickstarts }}" 45 | python: 46 | NAME: jenkins-slave-python 47 | SOURCE_CONTEXT_DIR: jenkins-slaves/jenkins-slave-python 48 | SOURCE_REPOSITORY_REF: "{{ cop_quickstarts_raw_version_tag }}" 49 | SOURCE_REPOSITORY_URL: "{{ cop_quickstarts }}" 50 | golang: 51 | NAME: jenkins-slave-golang 52 | SOURCE_CONTEXT_DIR: jenkins-slaves/jenkins-slave-golang 53 | SOURCE_REPOSITORY_REF: "{{ cop_quickstarts_raw_version_tag }}" 54 | SOURCE_REPOSITORY_URL: "{{ cop_quickstarts }}" 55 | gradle: 56 | NAME: jenkins-slave-gradle 57 | SOURCE_CONTEXT_DIR: jenkins-slaves/jenkins-slave-gradle 58 | SOURCE_REPOSITORY_REF: "{{ cop_quickstarts_raw_version_tag }}" 59 | SOURCE_REPOSITORY_URL: "{{ cop_quickstarts }}" 60 | mongodb: 61 | NAME: jenkins-slave-mongodb 62 | SOURCE_CONTEXT_DIR: jenkins-slaves/jenkins-slave-mongodb 63 | SOURCE_REPOSITORY_REF: "{{ cop_quickstarts_raw_version_tag }}" 64 | SOURCE_REPOSITORY_URL: "{{ cop_quickstarts }}" 65 | mvn: 66 | BUILDER_IMAGE_NAME: quay.io/openshift/origin-jenkins-agent-maven:4.2 67 | NAME: jenkins-slave-mvn 68 | SOURCE_CONTEXT_DIR: jenkins-slaves/jenkins-slave-mvn 69 | SOURCE_REPOSITORY_REF: "{{ cop_quickstarts_raw_version_tag }}" 70 | SOURCE_REPOSITORY_URL: "{{ cop_quickstarts }}" 71 | npm: 72 | BUILDER_IMAGE_NAME: openshift/jenkins-slave-base-centos7:v3.11 73 | NAME: jenkins-slave-npm 74 | SOURCE_CONTEXT_DIR: jenkins-slaves/jenkins-slave-npm 75 | SOURCE_REPOSITORY_REF: "{{ cop_quickstarts_raw_version_tag }}" 76 | SOURCE_REPOSITORY_URL: "{{ cop_quickstarts }}" 77 | zap: 78 | BUILDER_IMAGE_NAME: centos:centos7 79 | NAME: jenkins-slave-zap 80 | SOURCE_CONTEXT_DIR: jenkins-slaves/jenkins-slave-zap 81 | SOURCE_REPOSITORY_REF: "{{ cop_quickstarts_raw_version_tag }}" 82 | SOURCE_REPOSITORY_URL: "{{ cop_quickstarts }}" 83 | 84 | nexus: 85 | secret: 86 | SECRET_NAME: "nexus-password" 87 | USERNAME: admin 88 | PASSWORD: "{{ nexus_password }}" 89 | deploy: 90 | VOLUME_CAPACITY: 10Gi 91 | MEMORY_LIMIT: 2Gi 92 | CONTAINER_IMAGE: sonatype/nexus3:3.15.2 93 | 94 | sonarqube: 95 | build: 96 | NAME: "{{ sonarqube_name }}" 97 | SOURCE_REPOSITORY_URL: "{{ cop_quickstarts }}" 98 | SOURCE_REPOSITORY_REF: "{{ cop_quickstarts_raw_version_tag }}" 99 | SOURCE_CONTEXT_DIR: sonarqube 100 | FROM_DOCKER_IMAGE: sonarqube 101 | FROM_DOCKER_TAG: "7.7-community" 102 | FROM_DOCKER_IMAGE_REGISTRY_URL: "docker.io/sonarqube" 103 | postgresql: 104 | POSTGRESQL_DATABASE: sonar 105 | VOLUME_CAPACITY: 5Gi 106 | POSTGRESQL_PASSWORD: sonar 107 | POSTGRESQL_USER: sonar 108 | DATABASE_SERVICE_NAME: sonardb 109 | deploy: 110 | POSTGRES_DATABASE_NAME: "sonar" 111 | 112 | zalenium: 113 | NAMESPACE: "{{ ci_cd_namespace }}" 114 | IMAGE: "dosel/zalenium:latest" 115 | CPU_REQUEST: 200m 116 | MEMORY_REQUEST: 400Mi 117 | CPU_LIMIT: 1000m 118 | MEMORY_LIMIT: 2Gi 119 | 120 | hoverfly: 121 | build: 122 | NAME: "{{ hoverfly_name }}" 123 | SOURCE_REPOSITORY_URL: "{{ cop_quickstarts }}" 124 | SOURCE_REPOSITORY_REF: "{{ cop_quickstarts_raw_version_tag }}" 125 | SOURCE_CONTEXT_DIR: hoverfly 126 | deploy: 127 | NAMESPACE: "{{ ci_cd_namespace }}" 128 | MEMORY_LIMIT: 2Gi 129 | HOVERFLY_IMAGE_STREAM_TAG: "{{ hoverfly_name }}:latest" 130 | 131 | openshift_cluster_content: 132 | - galaxy_requirements: 133 | - pre_post_requirements.yml # Uses openshift-label role from casl-ansible 134 | # CI/CD builds are customisations to base software to enhance their functionality or make them OCP ready 135 | - object: ci-cd-builds 136 | content: 137 | - name: jenkins-s2i 138 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/jenkins-s2i-build/jenkins-s2i-build-template.yml" 139 | params_from_vars: "{{ jenkins.build }}" 140 | namespace: "{{ ci_cd_namespace }}" 141 | tags: 142 | - jenkins 143 | - jenkins-build 144 | - ci-cd-builds 145 | - name: tool-box 146 | template: "{{ cop_quickstarts_raw }}/{{ cop_quickstarts_raw_version_tag }}/build-docker-generic/.openshift/templates/docker-build-template.yml" 147 | params_from_vars: 148 | NAME: tool-box 149 | SOURCE_REPOSITORY_URL: "{{ cop_quickstarts }}" 150 | SOURCE_REPOSITORY_REF: v1.1 151 | SOURCE_CONTEXT_DIR: tool-box 152 | namespace: "{{ ci_cd_namespace }}" 153 | tags: 154 | - tool-box 155 | - ci-cd-builds 156 | - name: hoverfly 157 | template: "{{ cop_quickstarts_raw }}/{{ cop_quickstarts_raw_version_tag }}/build-docker-generic/.openshift/templates/docker-build-template.yml" 158 | params_from_vars: "{{ hoverfly.build }}" 159 | namespace: "{{ ci_cd_namespace }}" 160 | tags: 161 | - hoverfly 162 | - ci-cd-builds 163 | - name: sonarqube 164 | template: "{{ cop_quickstarts_raw }}/{{ cop_quickstarts_raw_version_tag }}/build-docker-generic/.openshift/templates/docker-build-template-override-FROM.yml" 165 | params_from_vars: "{{ sonarqube.build }}" 166 | namespace: "{{ ci_cd_namespace }}" 167 | tags: 168 | - sonarqube 169 | - sonarqube-build 170 | - ci-cd-builds 171 | 172 | # Secrets stored in OCP land and sync'd to Jenkins for consumption 173 | - object: ci-cd-secrets 174 | content: 175 | - name: nexus-secret 176 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/secrets/secret-user-pass-plaintext.yml" 177 | params_from_vars: "{{ nexus.secret }}" 178 | namespace: "{{ ci_cd_namespace }}" 179 | tags: 180 | - jenkins 181 | - secret 182 | - ci-cd-secrets 183 | - name: jenkins-secret 184 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/secrets/secret-user-pass-plaintext.yml" 185 | params_from_vars: "{{ jenkins.build }}" 186 | namespace: "{{ ci_cd_namespace }}" 187 | tags: 188 | - jenkins 189 | - secret 190 | - ci-cd-secrets 191 | 192 | # Jenkins slave agents to give him some superpowers in OCP land 193 | - object: jenkins-slave-nodes 194 | content: 195 | - name: jenkins-slave-agents 196 | template: "{{ cop_quickstarts_raw }}/{{ cop_quickstarts_raw_version_tag }}/.openshift/templates/jenkins-slave-generic-template.j2" 197 | params_from_vars: "{{ jenkins_slaves.build }}" 198 | namespace: "{{ ci_cd_namespace }}" 199 | tags: 200 | - jenkins-slaves 201 | 202 | # CI/CD Deployments is the OpenShift Deployment Configs and all 203 | # supporting tooling, pre and post hooks needed to setup and configure a comprehensive tool chain 204 | - object: ci-cd-deployments 205 | content: ## SONARQUBE DB DEPLOYMENT MUST COME BEFORE SONARQUBE DEPLOYMENT OR THE JDBC SECRETS WILL NOT BE CREATED PROPERLY 206 | - name: sonardb 207 | template: "openshift//postgresql-persistent" 208 | params_from_vars: "{{ sonarqube.postgresql }}" 209 | namespace: "{{ ci_cd_namespace }}" 210 | post_steps: 211 | - role: casl-ansible/roles/openshift-labels 212 | vars: 213 | target_namespace: "{{ ci_cd_namespace }}" 214 | label: "app=sonarqube" 215 | target_object: dc 216 | target_name: sonardb 217 | - role: casl-ansible/roles/openshift-labels 218 | vars: 219 | target_namespace: "{{ ci_cd_namespace }}" 220 | label: "app=sonarqube" 221 | target_object: svc 222 | target_name: sonardb 223 | - role: casl-ansible/roles/openshift-labels 224 | vars: 225 | target_namespace: "{{ ci_cd_namespace }}" 226 | label: "app=sonarqube" 227 | target_object: secret 228 | target_name: sonardb 229 | tags: 230 | - sonarqube 231 | - sonarqube-postgresql 232 | - sonarqube-postgresql-deploy 233 | - ci-cd-deployments 234 | - name: sonarqube 235 | template: "{{ cop_quickstarts_raw }}/{{ cop_quickstarts_raw_version_tag }}/sonarqube/.openshift/templates/sonarqube-deployment-template.yml" 236 | params_from_vars: "{{ sonarqube.deploy }}" 237 | namespace: "{{ ci_cd_namespace }}" 238 | tags: 239 | - sonarqube 240 | - sonarqube-deploy 241 | - ci-cd-deployments 242 | - name: nexus 243 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/nexus/nexus-deployment-template.yml" 244 | params_from_vars: "{{ nexus.deploy }}" 245 | namespace: "{{ ci_cd_namespace }}" 246 | post_steps: 247 | - role: infra-ansible/roles/config-nexus 248 | vars: 249 | nexus_namespace: "{{ ci_cd_namespace }}" 250 | nexus_user: "admin" 251 | nexus_password: "{{ nexus_password }}" 252 | nexus_api_base_path: /service/rest/v1 253 | tags: 254 | - nexus 255 | - nexus-deploy 256 | - ci-cd-deployments 257 | - name: jenkins 258 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/jenkins/jenkins-{{ jenkins_persistence_type }}-template.yml" 259 | params_from_vars: "{{ jenkins.deploy }}" 260 | namespace: "{{ ci_cd_namespace }}" 261 | tags: 262 | - jenkins 263 | - jenkins-deploy 264 | - jenkins-{{ jenkins_persistence_type }} 265 | - ci-cd-deployments 266 | - name: zalenium 267 | template: "{{ cop_quickstarts_raw }}/{{ cop_quickstarts_raw_version_tag }}/zalenium/.openshift/templates/zalenium-deployment.yml" 268 | params_from_vars: "{{ zalenium }}" 269 | namespace: "{{ ci_cd_namespace }}" 270 | tags: 271 | - zalenium 272 | - zalenium-deploy 273 | - ci-cd-deployments 274 | - name: hoverfly 275 | template: "{{ cop_quickstarts_raw }}/{{ cop_quickstarts_raw_version_tag }}/hoverfly/.openshift/templates/hoverfly-deployment-template.yml" 276 | params_from_vars: "{{ hoverfly.deploy }}" 277 | namespace: "{{ ci_cd_namespace }}" 278 | tags: 279 | - hoverfly 280 | - hoverfly-deploy 281 | - ci-cd-deployments 282 | - name: pact-broker 283 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/pact-broker/pact-broker-deploy.yml" 284 | namespace: "{{ ci_cd_namespace }}" 285 | tags: 286 | - pact-broker 287 | - pact-broker-deploy 288 | - ci-cd-deployments 289 | -------------------------------------------------------------------------------- /inventory/host_vars/ci-for-labs-ci-cd.yml: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | ansible_host: localhost 4 | ansible_connection: local 5 | 6 | build: 7 | NAME: ci-for-labs-ci-cd 8 | PIPELINE_SOURCE_REPOSITORY_REF: master 9 | PIPELINE_SOURCE_REPOSITORY_URL: https://github.com/rht-labs/labs-ci-cd.git 10 | RUN_POLICY: Parallel 11 | 12 | openshift_cluster_content: 13 | - object: ci-for-labs-ci-cd 14 | content: 15 | - name: pipeline 16 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/jenkins-pipelines/jenkins-pipeline-template-with-ocp-triggers.yml" 17 | params_from_vars: "{{ build }}" 18 | namespace: "{{ ci_cd_namespace }}" 19 | tags: 20 | - ci 21 | -------------------------------------------------------------------------------- /inventory/host_vars/projects-and-policies.yml: -------------------------------------------------------------------------------- 1 | --- 2 | ansible_connection: local 3 | 4 | 5 | jenkins: 6 | ROLE: admin 7 | PIPELINES_NAMESPACE: "{{ ci_cd_namespace }}" 8 | DEPLOYER_USER: jenkins 9 | 10 | image_puller: 11 | ROLE: "system:image-puller" 12 | PIPELINES_NAMESPACE: "{{ ci_cd_namespace }}" 13 | DEPLOYER_USER: default 14 | 15 | # Create new projects with a given short name and display name 16 | openshift_cluster_content: 17 | - object: projectrequest 18 | content: 19 | - name: "{{ ci_cd_namespace }}" 20 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/project-requests/create-project.yml" 21 | params_from_vars: "{{ ci_cd }}" 22 | action: create 23 | tags: 24 | - "{{ ci_cd_namespace }}" 25 | - projects 26 | - "projects-{{ ci_cd_namespace }}" 27 | - name: "{{ dev_namespace }}" 28 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/project-requests/create-project.yml" 29 | params_from_vars: "{{ dev }}" 30 | action: create 31 | tags: 32 | - "{{ dev_namespace }}" 33 | - projects 34 | - "projects-{{ dev_namespace }}" 35 | - name: "{{ test_namespace }}" 36 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/project-requests/create-project.yml" 37 | params_from_vars: "{{ test }}" 38 | action: create 39 | tags: 40 | - "{{ test_namespace }}" 41 | - projects 42 | - "projects-{{ test_namespace }}" 43 | 44 | # Bind user groups to roles for each of the new project eg giving ocp-devs edit access in the labs-ci-cd project 45 | - object: group-role-binding 46 | content: 47 | - name: "{{ ci_cd_namespace }}-acl" 48 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/role-bindings/group-rolebinding-template.yml" 49 | params_from_vars: "{{ edit_role_binding_group }}" 50 | namespace: "{{ ci_cd_namespace }}" 51 | tags: 52 | - "{{ ci_cd_namespace }}" 53 | - rolebinding-group 54 | - "rolebinding-group-{{ ci_cd_namespace }}" 55 | - name: "{{ ci_cd_namespace }}-acl" 56 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/role-bindings/group-rolebinding-template.yml" 57 | params_from_vars: "{{ admin_role_binding_group }}" 58 | namespace: "{{ ci_cd_namespace }}" 59 | tags: 60 | - "{{ ci_cd_namespace }}" 61 | - rolebinding-group 62 | - "rolebinding-group-{{ ci_cd_namespace }}" 63 | - name: "{{ dev_namespace }}-acl" 64 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/role-bindings/group-rolebinding-template.yml" 65 | params_from_vars: "{{ edit_role_binding_group }}" 66 | namespace: "{{ dev_namespace }}" 67 | tags: 68 | - "{{ dev_namespace }}" 69 | - rolebinding-group 70 | - "rolebinding-group-{{ dev_namespace }}" 71 | - name: "{{ dev_namespace }}-acl" 72 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/role-bindings/group-rolebinding-template.yml" 73 | params_from_vars: "{{ admin_role_binding_group }}" 74 | namespace: "{{ dev_namespace }}" 75 | tags: 76 | - "{{ dev_namespace }}" 77 | - rolebinding-group 78 | - "rolebinding-group-{{ dev_namespace }}" 79 | - name: "{{ test_namespace }}-acl" 80 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/role-bindings/group-rolebinding-template.yml" 81 | params_from_vars: "{{ edit_role_binding_group }}" 82 | namespace: "{{ test_namespace }}" 83 | tags: 84 | - "{{ test_namespace }}" 85 | - rolebinding-group 86 | - "rolebinding-group-{{ test_namespace }}" 87 | - name: "{{ test_namespace }}-acl" 88 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/role-bindings/group-rolebinding-template.yml" 89 | params_from_vars: "{{ admin_role_binding_group }}" 90 | namespace: "{{ test_namespace }}" 91 | tags: 92 | - "{{ test_namespace }}" 93 | - rolebinding-group 94 | - "rolebinding-group-{{ test_namespace }}" 95 | 96 | 97 | # Bindings to allow Jenkins operate outside of the project he's created in 98 | - object: service-user-role-bind 99 | content: 100 | - name: "jenkins-{{ dev_namespace }}-role-binding" 101 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/role-bindings/generic-service-user-bind.yml" 102 | params_from_vars: "{{ jenkins }}" 103 | namespace: "{{ dev_namespace }}" 104 | tags: 105 | - "{{ dev_namespace }}" 106 | - rolebinding-jenkins 107 | - "rolebinding-jenkins-{{ dev_namespace }}" 108 | - name: "jenkins-{{ test_namespace }}-role-binding" 109 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/role-bindings/generic-service-user-bind.yml" 110 | params_from_vars: "{{ jenkins }}" 111 | namespace: "{{ test_namespace }}" 112 | tags: 113 | - "{{ test_namespace }}" 114 | - rolebinding-jenkins 115 | - "rolebinding-jenkins-{{ test_namespace }}" 116 | 117 | # Add image puller role to be able to get images stored in other namespace 118 | - object: image-puller-role-binding 119 | content: 120 | - name: "image-puller-{{ dev_namespace }}-role-binding" 121 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/role-bindings/generic-service-user-bind.yml" 122 | params_from_vars: "{{ image_puller }}" 123 | namespace: "{{ dev_namespace }}" 124 | tags: 125 | - "{{ dev_namespace }}" 126 | - rolebinding-image-puller 127 | - "rolebinding-image-puller-{{ dev_namespace }}" 128 | - name: "image-puller-{{ test_namespace }}-role-binding" 129 | template: "{{ openshift_templates_raw }}/{{ openshift_templates_raw_version_tag }}/role-bindings/generic-service-user-bind.yml" 130 | params_from_vars: "{{ image_puller }}" 131 | namespace: "{{ test_namespace }}" 132 | tags: 133 | - "{{ test_namespace }}" 134 | - rolebinding-image-puller 135 | - "rolebinding-image-puller-{{ test_namespace }}" -------------------------------------------------------------------------------- /inventory/hosts: -------------------------------------------------------------------------------- 1 | [bootstrap] 2 | projects-and-policies 3 | 4 | [tools] 5 | ci-cd-tooling 6 | 7 | [apps] 8 | app-build-deploy 9 | 10 | [ci-for-labs] 11 | ci-for-labs-ci-cd -------------------------------------------------------------------------------- /meta/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | dependencies: 3 | -------------------------------------------------------------------------------- /minimal-ci-install.yml: -------------------------------------------------------------------------------- 1 | # This is a minimal playbook to be used when spinning up new clusters. 2 | # It will only install what is need to run the CI job we use for Labs CI/CD development. 3 | --- 4 | - name: Create Projects and Policies 5 | hosts: bootstrap 6 | tasks: 7 | - include_role: 8 | name: openshift-applier/roles/openshift-applier 9 | vars: 10 | include_tags: "{{ ci_cd_namespace }}" 11 | 12 | - name: Create CI/CD tools 13 | hosts: tools 14 | tasks: 15 | - include_role: 16 | name: openshift-applier/roles/openshift-applier 17 | tags: 18 | - openshift-applier 19 | vars: 20 | include_tags: "jenkins,ansible-slave" 21 | 22 | - name: Create CI Job 23 | hosts: ci-for-labs 24 | tasks: 25 | - include_role: 26 | name: openshift-applier/roles/openshift-applier 27 | tags: 28 | - openshift-applier 29 | - ci-for-ci 30 | -------------------------------------------------------------------------------- /pre_post_requirements.yml: -------------------------------------------------------------------------------- 1 | - src: https://github.com/redhat-cop/casl-ansible 2 | scm: git 3 | version: v3.11.2 4 | name: casl-ansible 5 | - src: https://github.com/redhat-cop/infra-ansible 6 | scm: git 7 | version: v1.0.10 8 | name: infra-ansible 9 | -------------------------------------------------------------------------------- /requirements.yml: -------------------------------------------------------------------------------- 1 | # This is the Ansible Galaxy requirements file to pull in the correct roles 2 | # to support the operation of CASL provisioning/runs. 3 | 4 | # From 'openshift-applier' 5 | - src: https://github.com/redhat-cop/openshift-applier 6 | scm: git 7 | version: v2.1.1 8 | name: openshift-applier 9 | -------------------------------------------------------------------------------- /site.yml: -------------------------------------------------------------------------------- 1 | # This is the default playbook and will create a standard (relatively large) install. 2 | --- 3 | - name: Create Projects and Policies 4 | hosts: bootstrap 5 | tasks: 6 | - include_role: 7 | name: openshift-applier/roles/openshift-applier 8 | 9 | - name: Create CI/CD tools 10 | hosts: tools 11 | tasks: 12 | - include_role: 13 | name: openshift-applier/roles/openshift-applier 14 | tags: 15 | - openshift-applier 16 | -------------------------------------------------------------------------------- /whats-in-the-box.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rht-labs/labs-ci-cd/b53d7949330f8cf2cd08a6c8d8036d75c83353ba/whats-in-the-box.png --------------------------------------------------------------------------------