The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Here at Moogsoft, we take quality seriously and one of the most important goals for our test suites is to catch issues early on in the development process. A lot of our automated tests are integrated into our CI/CD (Continuous Integration/Continuous Deployment) pipeline as gates that can block a merge request with quality issues. Therefore, to ensure stable CI/CD pipelines as well as quick and quality releases to production, it is important to have tests that are stable and lightweight.
At Cloudsmith, we pride ourselves in being the central source of truth for your packages and build artifacts. We provide one global platform to centralize your assets and give you the control and visibility that you need as part of a modern DevOps process.
Our 2020 SRE Report is ready! We launched the SRE survey 2020 this January with the goal of understanding the current state of SRE. The survey covered a range of topics including: As we neared the end of the survey period, the SRE community was in the midst of a sudden change. SRE teams were forced to migrate to all-remote IT. We realized we would not be able to provide an accurate analysis without considering this shift in how SRE teams were operating in this new environment.
Kubeflow Pipelines are a great way to build portable, scalable machine learning workflows. It is one part of a larger Kubeflow ecosystem that aims to reduce the complexity and time involved with training and deploying machine learning models at scale. In this blog series, we demystify Kubeflow pipelines and showcase this method to produce reusable and reproducible data science.
An SCM such as Git is more than just a database for source code. It’s not only the thing you need to interact with to get code to production, but also a log of changes on a project. It’s not just the last couple of weeks of commits that are worth looking at. Any commit remains relevant weeks, months and years later. A commit serves multiple purposes. The first one is to explain a change during its review and the second is to explain a change to a future reader.
