tag:blogger.com,1999:blog-27232680.post6193639137635376166..comments2024-03-20T06:54:32.435+01:00Comments on Plastic SCM blog: How we do trunk based development with Plastic SCMF3RD3Fhttp://www.blogger.com/profile/11524626976811746062noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-27232680.post-69686016043646857612017-04-09T13:22:10.584+02:002017-04-09T13:22:10.584+02:00That's quite cool!!
We implement Continuous D...That's quite cool!!<br /><br />We implement Continuous Delivery using Git (Git flow) on TFS, our CI system (Jenkins in our case) and some automation code written in PowerShell.<br /><br />We divide tasks and assign them at the beginning of every sprint in our planning and refinement meetings. The changes are developed in separate branches and at the end a pull request is created in TFS and assigned to the reviewers, which, in turn, can complete the pull request if everything is okay. The CI server is polling for changes every 5 minutes, perfoms a build and deploys into our DEV environment, calculates the next tag in Git and sends notifications via e-mail at the end. Then our QA team tests the changes in the DEV environment.<br /><br />Thus we ensure a stable deliverable product any time.<br /><br />We started this path more than 2 years ago when apparently lots of projects in the company didn't know about Continuous Delivery. One year later other teams in our project decided to adopt it as well. Several months ago we showed the process to our customer and he liked it a lot.<br /><br />Now other projects are beginning to use the same workflow and we are building some PowerShell scripting stuff flexible for different projects and needs.Anonymousnoreply@blogger.com