InfoQ Homepage IT Service Management Content on InfoQ
-
If Twitter Doesn’t Have a Staging Environment, Should Anyone?
With Twitter revealing they do not have a staging environment, how important is staging to delivering quality? When so many tasks are shifting to the developer these days and no one best developer approach fits all, how do dev teams determine the best developer methodology for them and their company?
-
Why Team-Level Metrics Matter in Software Engineering
In a world where everything can have perspective, context and data, it doesn’t make sense to limit that to just part of your software development process. The DORA metrics can provide insight into the health of your development environment, where value is being delivered and opportunities for improvement. Metrics must be used with careful insight to separate the signal from the noise.
-
Lessons Learned from Enterprise Usage of GitHub Actions
GitHub Actions is an effective CI tool. However, integrating it into enterprise organizations can be challenging. This article looks at best practices for GitHub Actions in the enterprise.
-
Blue-Green Deployment from the Trenches
Introducing blue-green deployments is often a beneficial improvement. However, with some architectures, it can be challenging to make the changes without impeding deployments. This article covers the challenges and lessons learned in implementing blue-green deployments in the real-world.
-
The Importance of Pipeline Quality Gates and How to Implement Them
A quality gate is an enforced measure built into your pipeline that the software needs to meet before it can proceed. This article covers how to get the maximum benefit from quality gates. Making good use of quality gates not only can improve the quality of your software, but it can also improve your delivery speed.
-
Bringing a Product Mindset into DevOps
To be successful, organisations need two things: products and services their customers find valuable, and the ability to deliver these products and services well. This article shows why we must design, implement and operate our delivery pipelines (the means of turning ideas into products in the hands of users) as we would any other product or service: by adding a “product mindset".
-
Why Observability Is the Key to Unlocking GitOps
In a GitOps work process, Git is the single source of truth for the system’s intended state. Observability can provide the missing piece: the single source of truth for the system’s actual state.
-
Successfully Integrating Dynamic Security Testing into Your CI/CD Pipeline
Dynamic security testing tools don’t require advanced cybersecurity knowledge to operate. Integrating DAST into your CI/CD pipeline should be done in stages by focusing on the riskiest areas first.
-
Why is Everything So Slow? Measuring and Optimising How Engineering Teams Deliver
As teams grow, they will slow down, but it should not mean that teams stop delivering value that can power future business growth. Avoiding excessive technical debt and ensuring systems are secure and performant becomes increasingly important. As an engineering leader, you can do things to be confident that your team is moving at the fastest and most sustainable pace.
-
Building an Effective Incident Management Process
A good incident management framework can help organizations manage the chaos of an outage more effectively leading to shorter incident durations and tighter feedback loops. This article introduces the components necessary for a healthy incident management process.
-
How Development Teams Can Orchestrate Their Workflow with Pipelines as Code
Infrastructure as Code was just the beginning. Configuration as Code followed shortly after – again becoming extremely commonplace and enabling organisations to scale their engineering capacity by a number of times. And in order to continuously increase the value development teams generate, Pipelines as Code is the natural consequence.
-
Analyzing Incident Data across Organizations: Courtney Nash on the VOID
The Verica Open Incident Database (VOID) is assembling publically available software-related incident reports. InfoQ talks with Courtney Nash on their recent findings including how MTT* metrics may not be beneficial, the average time to incident resolution, and the importance of studying near-miss reports.