#deploymentpipeline

[asadmukhtarr]

"Continuous Delivery" by Jez Humble and David Farley is a seminal book that provides a comprehensive guide to achieving reliable, rapid, and repeatable software delivery. The book outlines principles, practices, and techniques that enable teams to deliver high-quality software efficiently. Below is a user-friendly, step-by-step breakdown of the key outcomes and takeaways from the book, designed to help readers understand and implement continuous delivery effectively.

[bizessenceaustralia]

Bizessence is hiring Senior DevOps Engineer to reshape the landscape of infrastructure and continuous delivery. Ignite efficiency, automate deployments and guarantee unrivalled performance. Take the helm of innovative projects and catapult your career to extraordinary heights.

Don’t miss out on this chance!

To know more - https://bizessence.com.au/jobs/sr-devops-engineer/

[gfader]

Deployment VS Released in Lyft -> Discovering future product ideas: “Lyft Cash”

By reverse-engineering Lyft’s Android app, I came across a prototype of Lyft Cash in the payment page, which shows the balance, an option for “Auto Reload” and an option to add cash. 

Tapping the buttons on this prototype does nothing, which is understandable considering this feature is unreleased at the moment. I predict these buttons will become functional by the time of the feature release.

via Jane Manchun Wong https://wongmjane.com/blog/lyft-cash 

PS: 1st step in your organization: Distinguish  Deployed and Released. https://beyond-agility.com/deployment-vs-release/ 

[releaseteam]

via Twitter https://twitter.com/releaseteam

[releaseteam]

via Twitter https://twitter.com/releaseteam

[releaseteam]

#continuousdelivery Integration and Deployment (CI/CD) of #Microsoft https://t.co/j5tDi36jIR Core Application on #Azure Web App using #Jenkins #DevOps #deploymentpipeline Day1 https://t.co/5EC8cZwYWO via @AkhilMittal20

— Akhil Mittal (@AkhilMittal20) November 4, 2019

via: https://ift.tt/1GAs5mb

[releaseteam]

via Twitter https://twitter.com/releaseteam

[gfader]

Test automation *is not* a pre-requisite for Continuous Delivery

An interesting talk from Sally Goble (The Guardian Head Of Quality) from Porto Tech Hub Conference 2016)  https://www.youtube.com/watch?v=852OVo6HzcI

My notes: Minute 3:00 "Test automation is not a pre-requisite for Continuous Delivery" <ad>  For a definition of "Continuous Delivery" look here   http://gfader.tumblr.com/post/78335987657/do-you-know-the-difference-between-continuous </ad>

Minute 6:15 What they had before: * code freezes, go/no-go meetings, release managers, huge process, huge problems with delivery of software, massive regression testing suite Major issues: * #1 no deploy without downtime * #2 no rollback mechanism * #3 manual deploy process

Motto: "Not long wrong" I think this is focusing on MTTR (mean time to repair). Similar strategy at Facebook: "Real Men only Roll Forward"   http://gfader.tumblr.com/post/75704235866/real-men-only-roll-forward-quote

Can everybody use this approach? Maybe not * Self-driving cars? * Health or Safety critical environment?

How to mitigate risk? * Single Feature Releases  (including traceability) * Feature Toggles (Flags or Toggles called sometimes) * Monitoring and Alerting * Tests in low traffic areas (<-- high traffic area is covered by canary release) * Canary releases

Minute 19:30 Benefits of this approach: 1. Faster delivery benefited customers and stakeholders 2. Teams cared more when responsibilities were shared 3. Started adding value in unexpected ways -> testing != quality  (Dashboards, TestAutomation,...)

Minute 29:30 Adapt and evolve! Don't think that things that you were doing 2 years ago are appropriate doing now

Thoughts from myself after watching: * The whole team (including client) needs to be aware of the strategy * Are you empowered enough to fix issues immediately in Production? (Client relationship?) * Do you have enough traffic to run Canary Releases?

[gfader]

TFS vNext Feature Request: Fail build if CodeCoverage dropped over 1 day

Sad to see that this is still not part of TFS2012.

Rob described how to do this manually here http://scrumdod.blogspot.ch/2011/04/fail-build-if-code-coverage-is-low.html