.Net Squad. Deployments. Workflow. Namics
1 like817 views
The document describes the typical workflow of a .NET engineer on deployment day, detailing repetitive tasks such as checking source stability, pushing tested commits, and building solutions. It emphasizes the importance of code quality checks and successful completion of automated deployments. Additionally, it touches on the challenges faced during deployment, including potential issues with delivery servers.
.Net Squad. Deployments. Workflow. Namics
- 1. .Net Squad. Workflow. Quality. Namics. Daniel Scherrer. Software Architect. October 2015
- 2. Just a normal day as a .Net engineer. It’s Wednesday aka deployment day
- 3. Uff.. What I need to do? Let’s repeat…
- 4. Uff.. What I need to do? Let’s repeat… Check the stableness of my source the last time locally
- 5. Uff.. What I need to do? Let’s repeat… Check the stableness of my source the last time locally Push all tested commits to the source control system
- 6. Uff.. What I need to do? Let’s repeat… Check the stableness of my source the last time locally Push all tested commits to the source control system Let’s build the solution finally! This is the hardest time for all dev’s ;-)
- 7. Uff.. What I need to do? Let’s repeat… Check the stableness of my source the last time locally Push all tested commits to the source control system Let’s build the solution finally! This is the hardest time for all dev’s ;-) Check the source compliance and passing through all quality gates
- 8. Uff.. What I need to do? Let’s repeat… Check the stableness of my source the last time locally Push all tested commits to the source control system Let’s build the solution finally! This is the hardest time for all dev’s ;-) Push the release build with a version stamp to the deployment server Check the source compliance and passing through all quality gates
- 9. Yeah! That’s a piece of cake!
- 11. The code looks great!
- 12. …All null checks are implemented… …comments are there… ….very clean code… The code looks great!
- 13. …All null checks are implemented… …comments are there… ….very clean code… The code looks great! ok. I’m finished !
- 15. …talk with the Lead Tech about my code quality and create a merge request to master branch…
- 16. …talk with the Lead Tech about my code quality and create a merge request to master branch… … spend some minutes each week to view stats about my project or other commits of teammates
- 18. Yeah! Merge request accepted! Thx Tech Lead! ;-) Now, I can build and deploy…
- 19. Yeah! Merge request accepted! Thx Tech Lead! ;-) Now, I can build and deploy… Push the button «Run» and look few minutes to the screen… Or, hmmm… No, I will go to grab a coffee and talk about soccer with my project manager!
- 21. So, back to my laptop… Cool, the build finished and the automatic deploy to DEV is already done and succeeded, too!
- 22. So, back to my laptop… Cool, the build finished and the automatic deploy to DEV is already done and succeeded, too! Now, lets deploy to the staging environment and send a message to all testers…
- 23. So, back to my laptop… Cool, the build finished and the automatic deploy to DEV is already done and succeeded, too! Now, lets deploy to the staging environment and send a message to all testers… oops. I forgot the code quality check!
- 25. Let’s take a look on the sonar page…
- 26. Let’s take a look on the sonar page… … none blocker issues! … all quality gates are passed! … lucky punch!
- 27. No bugs found? Really? Hmm.. Ok let’s deploy to productive…
- 28. Ok, now, I’m getting nervous…
- 34. I love automatic deployments! DB Backups, Load Balancer configs, update servers, back to Load Balancer, all with one click!
- 35. Connection timed out? Ok, I must contact the Hoster- SysAdmin. Shit happens.. This is only one of many delivery servers… Longer than usual? 4 minutes running time? Ok, we must maintain this machine this week. I create an Issue for this…
- 36. Now, we are beginning to realise that we are LIVE…