InfoQ Homepage Automation Content on InfoQ
-
How Do We Automate Testing?
Test automation will demand time and attention, but when done the right way, is worth the investment. Don’t overdo automation; instead, focus on the needs and requirements. Having clean and easy-to-read code is very important to keep your test suite maintainable.
-
How Facebook Achieves Rapid Release at Massive Scale
A recent article about Facebook’s release process covers its flexible methodology of pushing massive amounts of code changes to production for web and native mobile apps. It focuses on how they moved from a “cherry-picking” to a “push-from-master” strategy over a period of one year and their tools and processes for achieving it.
-
Containers to Overtake VMs in Application Platform Space, Says SDxCentral Survey
One of the key findings of the 2017 Container and Cloud Orchestration Report from SDXCentral is that container adoption has steadily increased in the last two years and is set to overtake virtual machines (VMs) in the application platform space. In 2016, only 8% of respondents had deployed containers while this year, 45% are already using it.
-
Amazon Adds Target Tracking Support for EC2 Auto Scaling
Auto Scaling cloud resources is nothing new in AWS. However, Amazon recently announced a new Target Tracking policy that gives customers more granular control over how their application scales. Target Tracking policies allow an administrator to target a specific metric that will drive how and when the EC2 resources will scale.
-
How Testers Can Become More Technical
Testers who are able to successfully apply technical techniques of the testing craft during testing are more valuable; they increase both the quality and productivity of their teams. To become more technical, testers can learn something about code, and they should know how to manipulate and parse text files and how to use the most important analysis tools for their application platform.
-
Puppet Releases Its 2017 State of DevOps Report
The Puppet State of DevOps Report 2017 shows that high-performing IT teams are deploying more frequently and recovering faster. There is more focus on automation, with loosely coupled architectures and teams facilitating continuous delivery. Transformational leadership and lean product management practices are also key drivers behind high performing teams.
-
Bridging the Gap between Legacy Systems and Modern Techniques
Aging platforms that are managed with manual, time consuming processes can be costly. Teams can make a business case to management based on hours lost by repetitive work or re-work caused by human error for introducing modern techniques like automation tools and containers. The result is a predictable and repeatable process with minimal human interaction to deploy more often and more confidently.
-
Self-Service Operations: Better, Faster, Cheaper? Damon Edwards at DevOps Enterprise Summit
In preparation for the upcoming DevOps Enterprise Summit in London, InfoQ sat down with Damon Edwards, co-founder at Rundeck, Inc, and discussed the benefits and implementation of “Self-Service Operations”.
-
Jenkins Gets a Facelift with Release of Blue Ocean 1.0
Jenkins, the popular open source automation server that is used by development teams worldwide for continuous integration and continuous delivery pipelines, has recently announced the general availability of Blue Ocean 1.0.
-
Achieving Cloud-Native Operability
To drive operational maturity you need a microservices architecture, continuous delivery process, DevOps culture and platform automation. Together these four help you to transform your whole organization for achieving cloud-native operability to continuously deliver additional value to your customers.
-
Continuous Delivery at Klaverblad Insurance
Continuous delivery should be treated as an agile project as it is about automating your deployment. You have to speed up in small steps and gain trust by doing small deliveries and solve problems fast. The story about how Klaverblad insurance has implemented Agile, DevOps, continuous delivery, and microservices.
-
Microservices Imply a Distributed System
Moving towards microservices means moving towards distributed systems where you have to deal with latency, authorization and authentication, and messages that do not arrive, argues Sander Hoogendoorn. With microservices you can break down large systems into smaller components to regain control over the architecture.
-
DevOps Survival in the Highly Regulated Financial Industry
Robert Scherrer, head of application engineering at SIX, on how the company leveraged DevOps principles and benefits in the highly regulated Swiss financial industry. Engaging with compliance auditors to collaboratively agree on solutions early before it's too costly to change and avoiding legacy internal directives (not actually required by external regulations) are the main takeaways.
-
Design for Continuous Evolution: Immutable Model Is Key for Robustness
At QCon New York, Eric Brewer described how advancing from continuous delivery to fast and stable continuous evolution requires a discrete construction step to define an immutable model of the system. Brewer’s compute infrastructure design team uses Helm to construct and safely validate new deployment models, prior to attempting real deployment, although the concepts are technology agnostic.
-
Microsoft Introduces Flow for Citizen Cloud Workflow
On April 27, 2016 Microsoft announced a new personal workflow tool called Flow. The platform is an “IFTTT like” tool that focuses on the automation of personal tasks by orchestrating work across popular SaaS based services.