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



GIT is strictly source control.

Charles

On Mon, Feb 12, 2024 at 5:40 PM <smith5646midrange@xxxxxxxxx> wrote:

Offline question <<<<

The company I consult for wants their iSeries developers to use GIT. They
have a home grown change control system that installs source and objects
from environment to environment. I know you have a GIT product so I'm
thinking that you are a good person to ask this question.

Everything that I read about GIT says it is source control. I can't get
anyone at the company to walk me through a GIT "install". Is GIT strictly
source control or can it also handle object installation? If there is some
good documentation that you can point me toward, I have no problem reading
stuff.

Thanks for your time.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Richard Schoen
Sent: Monday, February 12, 2024 12:41 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: RE: Best way to convert from source PF to IFS source

FWIW: You don't have to move all your source to the IFS to get the goodness
of something like VS Code.

If you really just want to do a one time move I'm happy to give you a 7 day
trial license of iForGit to run the export process on your libraries.

You can export with or without source dates and source metadata info in the
headers. This can also set up structured repos for you in the IFS that you
can push to Github or any other remote git platform.

Then you just have to figure out the day-to-day compile processes all anew.

A more moderate approach would be to leave your source files intact and use
something like iForGit to export and manage your git source version
archival.

Then you can version to git equally from SEU, RDI or VS Code and even
custom
processes.

Or you can just roll your own utility or I recall Liam had something at one
point. Maybe even part of Code for IBMi for exporting.

https://www.iforgit.com

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
------------------------------

message: 6
date: Mon, 12 Feb 2024 11:19:55 -0600
from: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
subject: Re: Best way to convert from source PF to IFS source

Yea, I get that part, however one must move with current trends, and RDI is
becoming ever so difficult particularly with the latest disaster of moving
to 9.8, so we've moved on to VSCode for better or worse. Therefore the
direction that feels right is to use GIT, and that mostly eliminates your
need for source dates if implemented properly.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.


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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.



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.