Not sure if I saw any responses to this effect but here's a thought:
One way to approach this that might be SEU (old school) and RDi friendly would be to consider your IBM i source locations the master and do nightly syncs to github, SVN or wherever you want to capture changes.
Then the old-schoolers can work the way they want, but you're still capturing changes.
Then you could capture the source changes each night to an IFS/server or desktop location that could be a SVN or git repo.
Then you would commit the changes nightly.
Pretty simple poor-man's source capture.
It's worked for me in the past.
Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------
message: 5
date: Fri, 15 Jul 2016 09:28:39 -0400
from: John Yeung <gallium.arsenide@xxxxxxxxx>
subject: Re: Basic source control for RPGLE/CLLE/DDS
On Fri, Jul 15, 2016 at 4:26 AM, Paul Bailey <PabloMotte+Midrange@xxxxxxxxx> wrote:
The major problem I'm going to have after I've found a way to
implement a cheap source control is getting people to completely stop
their sloppy "just a quick fix" thinking, but one step at a time...
Indeed, culture is usually harder to change than technology.
I'm a source control neophyte, so maybe experienced folks can say right off the bat that this is not a good idea, but would it be possible to have automated nightly commits that ensure Git's picture of the world matches reality at least once a day? Obviously this would not take the place of proper, intentional commits, but it might minimize the impact of rogue code changes.
John Y.
midrange.com
