I assume by "CMS" you mean source control and not Content Management System.
I think there are two hurdles with using Git for ILE source.
1. Git requires stream files, and ILE source is traditionally stored in source PFs.
2. Traditional IBMi source control often handles things like builds and deployment, while Git is just for source control.
From: Jay Vaughn [mailto:jeffersonvaughn@xxxxxxxxx]
Sent: Wednesday, January 15, 2020 8:46 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: traditional AS/400 code base CMS transition
So, our company was just acquired by another company with deeper pockets and SoftLanding is asking an arm and a leg now to transfer the CMS to our new company.
So, we are exploring alternatives.
Could have up to 10-20 iseries devs working on the code base (which is large - hundreds for files/tables and thousands of pgms)
Is there a sharp learning curve for github enterprise (pro), compared to what we are used to now with TO?
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: traditional AS/400 code base CMS transition, (continued)
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.