[TestWarez 2017] Continuous Delivery and beyond
Continuous Delivery enables us to deliver software quickly and with high quality, ideally keeping our application production-ready with each code change, allowing us to ship that change right away. It is not a trivial process to introduce in a project or organization though. But can something as complicated as Continuous Delivery get even more complex? 'Shift left' approach to testing, risk analysis, consistent environments and build processes thanks to Chef, Vagrant and Jenkins Pipelines and a backlog that is possible to deliver in such methodology - these are only a few of elements that help us reach that goal. When going from monolithic architecture of our application to microservices realm a myriad of new challenges are born. How complicated our build pipelines get and how can we easily orchestrate them? What if your application is not as modular as you would like it to be? What if your client is not quite ready for the dynamics that CD brings? And most importantly, how to maintain the same quality level with the above problems? I would like to share my thoughts regarding these questions and on the future of DevOps in the quality-focused world. To gain the most from the presentation, the audience should be familiar with: microservices and monolithic architecture continuous delivery shift-left approach to testing the general idea about tools for configuration management, service discovery
Recommended
More Related Content
Similar to [TestWarez 2017] Continuous Delivery and beyond
Similar to [TestWarez 2017] Continuous Delivery and beyond (10)
More from Stowarzyszenie Jakości Systemów Informatycznych (SJSI)
More from Stowarzyszenie Jakości Systemów Informatycznych (SJSI) (20)
Recently uploaded
Recently uploaded (20)
[TestWarez 2017] Continuous Delivery and beyond
- 2. • • •
- 3. @automatingguy This Photo by Unknown Author is licensed under CC BY
- 5. @automatingguy This Photo by Unknown Author is licensed under CC BY-SA
- 8. Shift-left approach Risk analysis Test automation on multiple levels @automatingguy
- 9. @automatingguy Backlog Page types Features Common features JIRA Epic Epic Story/Task
- 10. @automatingguy This Photo by Unknown Author is licensed under CC BY-SA
- 32. @automatingguy
- 33. @automatingguy
- 34. @automatingguy
- 35. @automatingguy
- 36. @automatingguy
- 37. @automatingguy
- 38. @automatingguy
- 39. @automatingguy
- 40. @automatingguy
- 41. @automatingguy
- 42. @automatingguy
- 43. @automatingguy
- 44. @automatingguy This Photo by Unknown Author is licensed under CC BY-NC-SA
- 47. Core App 1 Solr Knot.x AEM App 2 Solr Knot.x AEM App 3 Solr Knot.x AEM @automatingguy
- 48. @automatingguy This Photo by Unknown Author is licensed under CC BY-NC-SA
- 49. Infrastructure Codebase Jira and tasks breakdown CI/CD Test automation Development & QA @automatingguy
- 50. Infrastructure Codebase Jira and tasks breakdown CI/CD Test automation Development & QA @automatingguy
- 51. @automatingguy This Photo by Unknown Author is licensed under CC BY-NC-SA
- 56. This Photo by Unknown Author is licensed under CC BY
- 58. Core Service A Knot.x Service B Knot.x App 1 Solr Knot.x AEM App 2 Solr Knot.x AEM App 3 Solr Knot.x AEM @automatingguy
- 59. Core Service A Knot.x Service B Knot.x App 1 Solr Knot.x AEM App 2 Solr Knot.x AEM App 3 Solr Knot.x AEM @automatingguy front-end front-end front-end
- 64. Build • Multiple repositories • Different branches Deployments & release • Different app contents Execution time • Parallelize as much as possible @automatingguy
- 65. @automatingguy
- 66. @automatingguy
- 67. @automatingguy
- 68. @automatingguy Core: url: 'https://bitbucket.org/url' branch: 'develop' credentials: 'creds' contents: - element: 'aem’ buildPaths: - 'aem' - 'aem/project-config' packageName: 'full’ active: false testJobs: - 'project-dev-bobcat-core’ - … sonarqube: - projectKey: 'project:project’ buildPath: 'aem' Images: … contents: - element: 'aem’ packageName: 'search-images’ - element: 'extensions’ moduleGroup: 'search-images’ - element: 'solr' … def steps = [:] echo "[Checkout] Preparing steps..." activeRepos.each { repo, cfg -> if(cfg.contents) { cfg.branch = params["${repo}Branch"] } steps[repo] = { dir(repo) { shallowClone from: cfg } } } steps.failFast = true echo "[Checkout] Executing steps..." parallel steps
- 69. • • @automatingguy This Photo by Unknown Author is licensed under CC BY-SA
- 71. @automatingguy
Editor's Notes
- Affected elements
- Tech stack: AEM web application Jenkins as CI/CD server + Jenkins pipelines Infrastructure-as-code
- Dev picks a story