Re: Basic source control for RPGLE/CLLE/DDS

What are your goals for implementing Git? More to the point, how do you
expect to implement those goals if you have colleagues who aren't on
board with using Git?

My primary goal is to have a cheap source control for RPGLE/CLLE/DDS source
because the legacy system we're working on all the time is 35 years old and
still being maintained regularly. The horse has bolted from the stable eons
ago, but there is still a long future in the software and a major
modernization change is coming up so (now that I have some influence) I
want to implement a source control system to at least catch the updates
from now on. Git is my number one choice at the moment purely because we
also work in Java/GWT for web development and all that is already
controlled with Git, so familiarity should help getting the team on board
with source control on the i. 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...

Your comment on iProjects inspired me to look at it again, but I was
disappointed again. I really need to find a way to make this work to save
myself another decade of "where did *this* come from?" headaches.


-Paul.


On 14 July 2016 at 16:14, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 7/14/2016 5:02 AM, Paul Bailey wrote:

Do you use the
iProjects feature of RDi? I was hoping somebody would say that was worth
the effort of learning because it appears to copy sources to the i before
compile, but everywhere I've seen uses various scripts they maintain
themselves.

My learning curve for iProjects was measured in minutes. I don't
maintain any external scripts; I compile with a right click.

When you copy the source back to the i for compile, do you have to

remember

to copy the /COPY books as well or do you keep a copy of the /COPY books

on

the i at all times?

You'll need to copy /every/ bit of source that is required.

I'm reticent to leave source on the i because I don't
want colleagues to think "i'll just make a quick change here" and the
change gets lost because it didn't get back to the repository for
whatever reason.

What are your goals for implementing Git? More to the point, how do you
expect to implement those goals if you have colleagues who aren't on
board with using Git?

--
--buck

Visit wiki.midrange.com and register for an account. Edit a page that
helps you, and because it's public, you'll help someone else, too!

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.