3. Git in the IBM i world
It is for all these reasons that it is so important for the IBM i world to take a serious interest in Git. Even if Git is not perfectly adapted to IBM i (for reasons we will explore later), its overriding advantage is that it naturally encourages dialogue and collaboration between developers from different technology backgrounds. Further, Git has the potential to quickly become the backbone of an IT organization by allowing staff to share the same code, innovation ideas and even development tools.
Let’s look more closely at this claim that Git is not “perfectly adapted” to the IBM i world. The reason boils down to architecture. In the world of distributed systems, the developer can work completely independently on his own machine. He can manage his source code, compile it, debug it and run it. In the IBM i world however, though the developer can manage his source code locally, he or she is absolutely required to be connected to the IBM i server for all subsequent tasks. So, this leads to the next question, “How do you manage multiple projects in parallel?”
For an in-depth look at that particular topic, I encourage you to reach the excellent blog article by our technical director, Michel Mouchon: Empower your IBM i teams: the extraordinary potential of Git.
4. ARCAD, indispensable for Git adoption
It is by resolving that challenge with Git on IBM i – the management of multiple projects in parallel – that ARCAD technology stands out on the market.
The ARCAD system was designed from the outset to manage development on as many parallel projects as needed, without imposing any constraints on the user. Each project is efficiently partitioned, managed and tracked and specific versions of programs can be tested independently of each other. This unprecedented degree of automation coupled with parallel streams of development naturally accelerates the rate of change, so that IBM i organizations can innovate more quickly, respond faster and deliver more functionality within each release. Accelerated and secure delivery serves to safeguard your organization’s strategic competitive advantage.
This is why most organizations who are adopting Git for IBM i development require the ARCAD technology layer. The way to be successful in adopting open source technology on IBM i is to complement the open source with commercial licenses from ARCAD. This model has many advantages:
– Smooth transition to industry standard tooling with a natural integration of technology,
– Seamless vendor guarantee of stability, security and efficiency of the open source integration layer,
– Built-in ARCAD DevOps methodology to reduce risk in the development process,
– Ecosystem around ARCAD’s development tools to refresh and modernize core IBM i team skills (training, consulting resources, etc.)
In short, this ARCAD-led approach to open source tooling on IBM i combines the best of both worlds, to secure the transformation of your teams and ready your IT organization for a faster, smarter future.