Jenkins is a free and open source automation server. Jenkins helps to automate the non-human part of the software development process, with continuous integration and facilitating technical aspects of continuous delivery. It is a server-based system that runs in servlet containers such as Apache Tomcat.
Builds can be triggered by various means, for example by commit in a version control system, by scheduling via a cron-like mechanism and by requesting a specific build URL. It can also be triggered after the other builds in the queue have completed. Jenkins functionality can be extended with plugins.
Unlike the integrations provided by Cyara (Jira, ServiceNow, PagerDuty, Splunk, etc.) where Cyara leverages vendor’s API(s), our CI/CD messaging is based on promoting and demonstrating how Cyara API’s are the path for including “Continuous Testing” as part of the CI/CD pipeline. If you ask: “Why Jenkins?”, or “What makes Jenkins special?”, the answer is that Jenkins is one of the more frequently mentioned CI/CD automation software. That said, we are not tied to any CI/CD software and simply using Jenkins as an example of how the power of Cyara CX Platform can be leveraged in the CI/CD environment.
Continuous integration (CI) is a coding philosophy and set of practices that drive development teams to implement small changes and check in code to version control repositories frequently. Because most modern applications require developing code in different platforms and tools, the team needs a mechanism to integrate and validate its changes.
The technical goal of CI is to establish a consistent and automated way to build, package, and test applications. With consistency in the integration process in place, teams are more likely to commit code changes more frequently, which leads to better collaboration and software quality.
Continuous delivery (CD) picks up where continuous integration ends. CD automates the delivery of applications to selected infrastructure environments. Most teams work with multiple environments other than the production, such as development and testing environments, and CD ensures there is an automated way to push code changes to them. CD automation then performs any necessary service calls to web servers, databases, and other services that may need to be restarted or follow other procedures when applications are deployed.