× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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.

-----Original Message-----
From: Richard Schoen [mailto:Richard.Schoen@xxxxxxxxxxxxxxx]
Sent: Wednesday, October 25, 2017 4:03 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Git for RPG source code management

Why not leave the source where it is in the source files and do a regular daily push of changed members to an IFS or network folder and commit to GIT.

Then the master is still IBMi source files, but changes to source can get pushed regularly a well as backed up nightly with standard IBMi backups.

Not a full source control system but an option especially since you already use .Net, IBMi and Git.

Regards,


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

-----Original Message-----
From: Matt Olson [mailto:Matt.Olson@xxxxxxxx]
Sent: Wednesday, October 25, 2017 1:24 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Git for RPG source code management

All,

I've read this over: http://yips.idevcloud.com/wiki/index.php/PASE/Git

However, it seems to want the Git server running on the IBM i.

We already have a Git Server (VSTS/TFS Online). We don't want another one.

What would be the steps to store all our source code on a remote Git repository so that we can get all the advantages VSTS / TFS provides you (code reviews, source code check-ins to bug/workitem linking, sprint planning, global source code searching).

Matt




--
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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.