Re: create an archive of a source member each time changed -- MIDRANGE-L

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

Eric Bothes,
I suppose you could, but . . . The only archive needed is a single archive/snapshot of fully tested code being deployed to production.
Example: If you deploy an application 5 times to production environment over 3 years, you just need an archive of each time you deployed to production, that is, 5 archives.
Be sure to bundle into that archive all the source dependencies so that you can recover and recompile to any version/release in the past.
There is NO VALUE in archiving every edit/save of source code because you may have 2 to 75 successive edits of source that happen before the code is fully debugged and ready to be deployed to production.
Archiving 74 successive edits that will never deploy to production environment would be an extreme waste of resources.
Eric Lehti (retired from 40 years on IBMi on Power and its predecessors)

On Nov 7, 2024, at 9:35 AM, eric bothes <iseriesstuff@xxxxxxxxx> wrote:

I'm looking for a way to create an archive of a source member each time it is changed using seu/etc.

basically want to keep a history of any changes.

is there an api/trigger or something where i can run an archive process prior to changes being saved to a source member?

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.