If you haven't implemented source version control on your IBM i system yet, but have a need to start easily capturing source member versions of your classic source from source physical files, we have you covered.
In iForGit V1.25 a new feature has been added to handle simple source member version control for a team that isn't quite ready for using Git. And once ready for Git, the simple source management commands can still be used to manage moving source between production and development libraries if the source master versions will continue to live on IBM i in source physical files.
Developers can:
Check out a source member copy to their development or test libraries to work on the source. The source member can also be removed from the production library while being worked on if desired. Archive snapshots are always taken before and after source member checkouts so that no source ever gets lost.
Check in a source member copy from their development or test libraries after completing work on the source. The checked in source member can be removed from the development library when checked in. Or a copy of the development source can be left in the development library once checked in for further work. Archive snapshots are always taken before and after source member check-ins so that no source ever gets lost.
Capture an instant point-in-time archive snapshot of ANY source member at any time for backup purposes. This is helpful when working on a source member and you don't want to have multiple named copies of the source member lying around. Just take a snapshot and get to work on the source member changes.
A database log is kept for all archive source versions so developers can easily identify an old source member by reviewing the log file.
Getting started with source management has never been easier with the new Simple Source Management Commands built-in to the iForGit software.
For more information to make your source management life easier, visit: https://www.iforgit.com and request more info. Or feel free to email: info@mobigogo.net
No comments:
Post a Comment