tfh111517-story02-fig01
November 14, 2017 Timothy Prickett Morgan
November 14, 2017 Timothy Prickett Morgan
Tags:
In this 3-Part webinar series, we will lay out a plan for a Phased and Step-by-Step Approach to DevOps. Starting with a simple IBM i workflow in ARCAD’s “classic” DevOps suite, we’ll upgrade to Git for source control along with Azure DevOps (or Jenkins) for automated CI/CD. And finally, we’ll introduce testing and code quality tools to achieve a complete DevSecOps pipeline on IBM i.
Don’t miss this Series to see how to smooth your DevOps adoption on IBM i!
Part 1: “Classic” without Git
Thursday, April 11 (30 minutes) 12pm ET
Speakers: Ray Bernardi and Alan Ashley
Take the first step in a practical IBM i approach with “classic” ARCAD for DevOps (without Git). Migrate from an in-house process or upgrade from a legacy tool to one that is more functional, automated, and extensible. Join us to see:
We’ll set the stage for Part 2, ready for pipeline automation and Git with the same components, same workflow and same IDE!
Part 2: Git & CI/CD
Thursday, April 18 (30 minutes) 12pm ET
Speakers: Jeff Tickner and Alan Ashley
Take automation to the next level with Git and an orchestrated CI/CD pipeline! In our example, we’ll use Azure DevOps, but you can achieve the same with Jenkins, Bamboo, or another tool of your choice. Whether you use RDi, VS Code or 5250, upgrading to Git is easy, and we keep your same workflow and metadata. Join us to see:
Spoiler alert — .net developers love the integration and the visibility of active changes
Part 3: Quality & Test
Thursday, May 9 (30 minutes) 12pm ET
Speakers: Ray Bernardi and Alan Ashley
Build out the full pipeline with automated unit testing and code quality checking. ‘Shift defects left’ to detect errors early in the development phase, from either RDi or VS Code. Join in to see:
Copyright © 2024 IT Jungle