[Webinar] “Git Together”: green screen and RDi together over Git

Have you started using Git on IBM i?  Welcome to a cool new world of:  unique source code repository, concurrent versioning, and collaborative tooling essential for effective development today.

But moving to Git is a challenge for many IBM i shops, who risk losing some powerful change management features with “Git standalone”.

Now with ARCAD V11, you can take a progressive path to Git and gain the “best of both worlds”: traditional and RDi teams over a common Git repository, retaining all the features that IBM i developers love:

• Git automation for both RDi and traditional development
• Deep integration with collaborative Git tooling (e.g. GitHub)
• Optimized IBM i project view for Git with change history
• Automated “smart dependency“ build 

Watch our Webinar to gain all the benefits of Git and Jenkins coupled with powerful IBM i release management for both your traditional and new teams.

Ray Bernardi is a 30-year veteran involved in the System 38/AS/400/iSeries/IBM i development and currently is a Pre/Post Sales technical Support Specialist for ARCAD Software, international ISV and IBM Business Partner.  Ray has been involved with the development and sales of many cutting edge software products throughout his career, with specialist knowledge in Application Lifecycle Management (ALM) products from ARCAD Software covering a broad range of functional areas including enterprise IBM i modernization and DevOps.  In addition, Ray is a frequent speaker at COMMON and many other technical conferences around the world and has authored articles in several IBM i publications on the subject of application analysis and modernization, SQL, and business intelligence.

Andrew Clark has been working on the IBM i platform for more than 30 years, beginning with the “secret Mankato Project” on a pre-release version of os/400, and an internship at IBM Rochester working on the Query team. He has development expertise in more than a dozen languages on multiple platforms, as well as a background in green-screen, Windows, mobile and web development. His major responsibilities included coordinating developers from four different offices in three different continents while still maintaining Architect responsibilities. He is proficient at everything DB/SQL on IBM i, and has extensive experience in the entire DevOps lifecycle.