On 8/3/2015 11:49 AM, Robert Mullis wrote:
We are looking for a CMS system. I was under the impression that eGit (or
git) didn't recognize source files.
It doesn't. The basic idea is that you set Git up to monitor an
iProject directory. Changes that happen there can then be committed
locally to your PC or pushed to a repo on the i side - or onto any file
server. Then other developers can pull from the remote repo to their
local repo and be working with the same tree.
Git is NOT a change management system! It only, only, only handles
source versioning. Deploying objects is still a manual process. Git is
only a small part of the problem that a true CMS solves. Imagine having
to deploy an RPG program, a display file, and a data queue. YOU have to
compile these against the right libraries, YOU have to deploy them into
the right libraries and YOU have to keep track of all the pieces parts
that make up this particular deployment.
It sounds like Git has a lot of limitations. Yes, it does. In places
where Git is used, Ant or Make are also used for the deployment. I
don't find either of those much better than manual deployment, so I
don't use them. I am using Git because I like being able to see when
the code changed, what in the code changed and all of the pieces that
changed with it. So, limited as it is, it has value to me.
If I had the budget for a true CMS, I'd drop Git in a heartbeat.
midrange.com
