Re: Git for RPG source code management

Hi Matt,
Our company has created a free open source project "Better Object Builder"
(BOB) (https://github.com/s4isystems/Bob). that gives you the ability to
store all your IBM i objects in GIT or GitHub and build them using BOB.

We have moved all our source (RPG, CLLE, DDS, C/C++, JAVA, PNLSRC, ect) off
the I and to GitHub. Each developer has their own Git personal repository,
a build directory in the IFS and an IBM i build library for testing. In
addition, because all commits to Git are identified and stored in GitHub we
can move a series of changed code to test and production or easily reverse
changes or even go back multiple releases.

We have created programs to initially copy source from the QSYS file system
to the IFS and programs to build our product distribution files.

Each developer uses their favorite tools to maintain the source in their
own repository but most use RDI since BOB comes with tools to assist our
development using the RDi IDE.

BOB puts i development in alignment with the remainder of the world. You
will need to learn Git, how to create a makefile, shell commands
and potentially scripting.

BOB is free and available under the Apache License. Check the Wiki pages on
GitHub.

Spencer

On Wed, Oct 25, 2017 at 8:58 PM, Richard Schoen <
Richard.Schoen@xxxxxxxxxxxxxxx> wrote:

Sounds like if you want something unified you should look at Arcad or one
of the other providers that works with multiple repositories such as Git
and TFS and also IBMi.

I have no experience with it but did a quick google search.

Better than trying to hammer something yourself to download, upload,
commit, build,etc if you want one unified solution.

iProjects in RDP might work, but very klunky to work with. Although I
think they hook up to Rational Team Concert.

Still might end up with one process for IBMi source and another for .Net,
Java, etc.......

That's why I like my idea of letting source files still be the master and
do daily Git commits to your TFS/Git repo.

Don't try to fix the old IBMi paradigm but manage your source with a combo
of old and new.

Share with us what you find.

Regards,

Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------

message: 4
date: Wed, 25 Oct 2017 21:20:43 +0000
from: Matt Olson <Matt.Olson@xxxxxxxx>
subject: RE: Git for RPG source code management

All our other source code is hosted in TFS using Git as the repository
engine. That is the "master" repository.

What users work on should be a local copy of the master repository and
push changes up to the master repository when they are ready.

I should be able to do this from a laptop, disconnected from the network.
Which is one of the features of Git.

Additionally, we want all the companys source code in one place so we can
have unified tracking of it (linking specific RPG Git push's to specific
work items, pull request linking, etc.). Basically the full life cycle of
software development is tracked there in a much more robust manner than we
have available on the IBMi.

I am trying to find how folks who have implemented Git for RPG source have
done it. Specifically the mechanics of where the RPG source code resides
(users machine or IFS). I'm hoping NOT IFS as that limits your "work on RPG
anywhere" feature of Git.

Also, I want to know if RDP "pushes" the source code to the IBMi from the
users local C: drive for the purposes of compiling (someday we may get a
RPG compiler that runs locally on the users machine ?)

If we "push" to the IBM I's git repository instead of our current Git
repository in TFS we will have no way to link it to work item # 967, and
subsequently pull request 252 for full code review traceability and work
item linking.


--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD