Josh Baer from Spotify about CI/CD for Machine Learning
Josh Baer from Spotify talks to Iguazio (https://www.iguazio.com/) CEO Asaf Somekh about the challenge of bringing CI/CD to machine learning
Josh Baer from Spotify talks to Iguazio (https://www.iguazio.com/) CEO Asaf Somekh about the challenge of bringing CI/CD to machine learning
“Quality at Speed” is the new norm in software development. Enterprises are making their moves toward DevOps methodologies and Agile culture to accelerate the delivery speed and ensure product quality. In DevOps, a continuous and automated delivery cycle is the backbone that makes fast and reliable delivery possible. This results in the need for proper continuous integration and continuous delivery (CI/CD) tools.
You’ve likely heard of the term CI/CD pipeline. You have probably known about these practices: continuous integration, continuous delivery, and continuous deployment as well. But the uncertainty remains: What are the differences between continuous delivery and continuous deployment? Which one should you apply to your CI/CD pipeline? How are these terms related to one another? How to find out which one suits your team best?
In this blog I would like to highlight a new capability from our latest 7.2 Studio and its integration with Talend Cloud in the Summer ‘19 release. While this feature could be seen as a light improvement aiming to ease the life of Talend users, it’s in fact much more than that! While Talend has been delivering CI/CD capabilities for a very long time, the continuous integration tools landscape is evolving fast.
The third wave of test automation brings about more concepts in software delivery – one of which is ‘continuous testing.’ However, mastering continuous testing is difficult; choosing the right continuous testing tool is even more overwhelming.
Continuous Integration and continuous delivery (CI/CD) is a complex part of any development cycle. It involves continuously integrating code into a shared repository to keep code progression amongst a team of developers running smooth and steady. This helps prevent merging errors, duplicated efforts and promoting collaboration to create a better product. That code is then thoroughly and continuously tested to keep problems from arising.