- From The Pipeline v36.0
- From the Pipeline v9.0
- From the Pipeline v15.0
- From the Pipeline v14.0
- From the Pipeline v13.0
- From the Pipeline v12.0
- From the Pipeline v11.0
- From the Pipeline v10.0
- From the Pipeline v8.0
- From the Pipeline v17.0
- From the Pipeline v7.0
- From the Pipeline v6.0
- From the Pipeline v5.0
- From The Pipeline v4.0
- From the Pipeline v3.0
- From the Pipeline v2.0
- From the Pipeline v16.0
- From the Pipeline v18.0
- From The Pipeline v35.0
- From The Pipeline v28.0
- From The Pipeline v34.0
- From The Pipeline v33.0
- From The Pipeline v32.0
- From The Pipeline v31.0
- From The Pipeline v30.0
- From The Pipeline v29.0
- From the Pipeline v27.0
- From the Pipeline v19.0
- From the Pipeline v26.0
- From the Pipeline v25.0
- From the Pipeline v24.0
- From The Pipeline v23.0
- From the Pipeline v22.0
- From the Pipeline v21.0
- From the Pipeline v20.0
- From the Pipeline v1.0
The following will be a regular feature where we share articles, podcasts, and webinars of interest from the web.
That Salesforce outage: Global DNS downfall started by one engineer trying a quick fix
Salesforce encountered a global outage after a change applied to DNS servers rendered customer unable to access the products. This occurred because a script to handle a DNS change contained a bug that would cause a timeout under load. Since the change was pushed globally, a timeout occurred and took down Salesforce. What is curious is how the company that prides itself on DevOps practices would allow for one change to take down their applications. Also worrisome is the company threw a single engineer under the bus when it’s apparent that both process and infrastructure could be improved. It won’t encourage other engineers to make changes without covering their butts in the future or have people be forthcoming in postmortems.
Integrate Manual and Automated Testing in a Test Plan
In an older post, Art Trevethan advises on how to balance automated and manual testing with an “automate 20% of test cases” approach. He first looks at identifying the test cases that take up an inordinate amount of time, then shifts into the financial aspect of how much value automation provides. Art also provides hood advice on the tools a team should use.
Intro of DevOps Dojo
Microsoft has released a Dojo as a Lean Product which requires an inspiring vision, clear mission, focused strategy, human-centric design, and committed execution. They are making DevOps a standard software delivery method at Microsoft Services. The DevOps Dojo is a community of practice at Microsoft that started from the Services organization, and then expanded to Customer Success, Digital Advisory, Product Groups, and other organizations.
How to Scale Automated Testing With Jenkins
Eran Kinsbruner provides insight on how to best leverage Jenkins to help expand automated testing. He first starts by creating a shared understanding of CI/CD and where continuous testing fits. He walks through common challenges to using Jenkins for continuous testing and then provide several patterns to implementation. Eran links a video with a how-to on setting up a pipeline for continuous testing.
Security keys are now supported for SSH Git operations
GitHub has been at the forefront of security key adoption for many years. They were an early adopter of Universal 2nd Factor (“U2F”) and were also one of the first sites to transition to Webauthn. They’re always on the lookout for new standards that both increase security and usability. GitHub is taking the next step by shipping support for security keys when using Git over SSH.