I assume by "CMS" you mean source control and not Content Management
I think there are two hurdles with using Git for ILE source.
1. Git requires stream files, and ILE source is traditionally stored in
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
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?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
Please contact support@xxxxxxxxxxxx for any subscription related
Help support midrange.com by shopping at amazon.com with our affiliate
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.