When Elastic started to use Jenkins, there was already a dedicated group providing the service, so teams were encouraged to handle their automation using the Configuration as Code paradigm with the Jenkins Job Builder tool. However, once adoption reached a certain threshold, this particular approach didn’t scale. The organization realized they needed to consider about a more robust, testable and automated CI/CD service.
Elastic started by applying the following principles and practices:
Everything is tested
Join this session to learn more about Elastic's journey with Jenkins, including the personal experience of their teams and long-term vision.