Operations | Monitoring | ITSM | DevOps | Cloud

We get it, installing Artifactory and the JFrog DevOps Platform on Kubernetes can be daunting. As easy as we’ve sought to make it with our official JFrog installation Helm charts, there are a lot of decisions to be made. That’s meant to give you the widest possible choice for how to best fit your JFrog installation to your infrastructure. But choice can be overwhelming, too.

A typical modern DevOps pipeline includes eight major stages, and unfortunately, a release bottleneck can appear at any point: These may slow down productivity and limit a company’s ability to progress. This could damage their reputation, especially if a bug fix needs to be immediately deployed into production. This article will cover three key ways using data gathered from your DevOps pipeline can help you find and alleviate bottlenecks in your DevOps pipeline.

Continuous Deployment (CD) requires setting up your infrastructure and automation to update your solution with the latest code change from the main branch. That’s what we call “Liquid Software”. Full automation makes your deployment seamless, less error prone, faster and it makes the feedback loop shorter because you can now deploy after each change. Achieving continuous deployment requires the following elements.

Bitbucket Pipelines now allows steps with a manual trigger to be used in parallel groups, satisfying one of the highest voted feature requests. This feature provides more flexibility in Pipelines, allowing teams to configure pipelines with multiple options and then only run the steps they actually need to run, at the time they want. For example you can choose which environments should be deployed for individual developers, giving them different environments to test and do their work.

Continuous Integration (CI), Continuous Delivery (CD) and Continuous Deployment (CD) are three processes that automate integrating software development into a product and deploying the modified product to test and production environments.