It’s hard to talk about Jenkins without also talking about Git, and that’s because the two go hand in hand. One of the reasons developers tend to love Jenkins is it gives them more visibility into things that typically are “ops” side. SCM is the backbone of any pipeline, so it makes sense that the infrastructure configuration would be stored in the same Git repository as any other code. Doing so means all commits are traceable, and are pushed through the same pipeline. Your same governance and testing can apply to not just application source, but infrastructure configuration as well. Arcad plugins can support both freestyle and pipeline (configuration-as-code) models.
Note: If you’d like to learn more about Git on IBM i, you can watch our webinar here.
4. Jenkins on i
Jenkins was designed for x86 platforms and on its own has limited capabilities on the IBM i platform. Arcad changes that, with our collection of Jenkins plugins that allow for automation through the stages of build, code quality, test, and deploy.
Arcad Builder is the intelligent build engine built on Arcad’s cross reference repository. With Arcad Builder, you will never have to manage libraries, look for dependencies, or manually copy source, Builder handles everything automatically. With our Jenkins plugin, all you have to do is push your code, and an Arcad Build is executed with the correct project parameters.
Arcad CodeChecker is a code quality tool for RPG & SQL. With CodeChecker you can enforce a baseline standard of quality for your code base, as well as enforce business and security rules. When plugged into a DevOps pipeline this tool becomes incredibly powerful. Any new code is automatically checked for quality and security, and developers instantly know if something isn’t up to standard. This is great not only from a security perspective, but also helps on-board new developers, as they have a tool to help them learn the business rules without someone watching over their shoulder.
In order to truly integrate RPG/COBOL into your DevOps pipeline, automated testing is a necessity. Arcad has tools for both unit and regression testing and both can be automated with our Jenkins plugins. Incorporating automated testing helps you shift left, ensuring bugs or defects are caught early on and before they grow costly.
Note: Read more about the benefits of Unit testing here.
No matter how complex your deployment requirements, it can be completely automated with Drops. Whether you are deploying to IBM i LPARS, or Windows/Linux servers, Drops is a truly platform agnostic application release automation solution. While Drops is a fully capable automation server in its own right, it can also be orchestrated by CloudBees CI to hook into your existing pipeline.
5. Better together
As you’ve hopefully learned, Arcad and CloudBees together complete an adhesive solution across legacy and distributed. With great support, scalability, and enhanced security and stability, CloudBees CI is an obvious choice for any enterprise. And with Arcad’s deep integration, it’s never been easier to implement a complete DevOps pipeline. A chain is only as strong as its weakest link, and many IBM i development teams are lacking the tools they need to succeed. What you have seen today is a way to empower all your teams by standardizing on one DevOps pipeline, breaking down silos in the process.