What is Mean Time to Recovery (MTTR)?
MTTR is defined by DORA and in the Accelerate book as '"how quickly a service can be restored after a failure". Learn more about this engineering productivity metric in this 2-minute explainer video.
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
CI CD
The latest News and Information on Continuous Integration and Development, and related technologies.
What is Change Lead Time?
Change Lead Time is defined by DORA and in the Accelerate book as '"the time it takes to go from code committed to code successfully running in production". Learn more about this engineering productivity metric in this 2-minute explainer video.
What is Change Failure Rate?
Change Failure Rate is defined by DORA and in the Accelerate book as '"the percentage of changes to production, including for example software releases and infrastructure configuration changes, that fail". Learn more about this engineering productivity metric in this 2-minute explainer video.
Managing reusable pipeline configuration with object parameters
CircleCI pipelines are defined in configuration files using the YAML syntax, which has been widely adopted by many software tools and solutions. YAML is a human-readable declarative data structure commonly used in configuration files and in applications where data is being stored or transmitted. The data in pipeline configuration files specifies and controls how workflows and jobs are executed when triggered on the platform.
DORA Metrics Explained: the four DORA metrics and how to improve them
DORA metrics come from an organization called DevOps Research and Assessment. This was a team put together by Google to survey thousands of development teams across multiple industries, to try to understand what makes a high performing team different than a low performing team. What they ended up settling on are these four metrics.
GitOps Feature Release
It’s no secret that the software development community is starting to embrace GitOps. With the complexity of engineering modern software today, it is becoming a necessity for many companies to reassess their software development and delivery practices. When Codefresh first released GitOps 2.0 late last year, we had already planned to make it a core pillar of our platform.
Codefresh GitOps Controller
The new Codefresh GitOps dashboard gives you the perfect overview of your deployments and how they change over time. This powerful view combines information from multiple sources such as your Kubernetes services, Git Pull Requests, and JIRA issues. To help you incorporate all of this helpful information into your deployments, we have introduced the GitOps controller, a handy agent that is installed in your cluster and collects critical information about your GitOps deployments.
GitOps Current State Dashboard
At Codefresh, we are fortunate to hear from customers of all sizes and nearly every industry. A common interest is visibility into deployments and their respective environments. As a company filled with software enthusiasts and developers, this strongly resonates with our culture and our passion for empowering developers. Visibility has been an area of continuous improvement for Codefresh and something we are committed to being the best at.
Codefresh GitOps App of Apps
Microservices are powerful, but it isn’t a secret that they come with many challenges. Codefresh is acutely aware of this as we built our platform on microservices. We know what it means to maintain a fast-moving and complex software service that must remain highly available. One of the most common challenges we deal with is maintaining complex relationships at deployment time among individual microservices.