NetIQ allows you to manage Designer package versions using Git. Git is an open source distributed version control system used for storing and retrieving files. It allows you to manage, track, maintain the history of changes, or retrieve an earlier state or compare different states of files. For more information about Git, see Git documentation.
IMPORTANT:You can use Git to share packages when the packages are developed or staged. NetIQ does not recommend you to use Git for Designer project versioning.
Implicit backup: Git maintains multiple backup copies within the repository. This is useful in case of an event or disk crash.
Pull and Push operation: Git allows you to copy changes to a remote or local repository.
Theoperation fetches the changes from the Git repository to a local repository. This is useful when you want to synchronize changes between the two repository instances.
Theor operation publishes the changes from the staging area to a local repository and further publish them to the Git repository. You can also publish your changes directly from the staging area to the Git repository.
You must create a source Git repository and add the required files to it. Designer pulls files from the Git repository. The changes are first performed on the. Then the changes are staged in the before they are pushed to the Git repository.
Working Tree: This consists of the files that you are currently working on. You can add, modify, or delete a file from the local code base location. You can modify multiple files at a time. You add the changes to theonce you have modified the required information.
Staging Area: This is an intermediate storage area. This area has the changes that were made to the files in the. Git collects all changes which will be part of the next commit action from this area.
Git Repository: This is the area that stores all the committed changes. The final version of the changes are available in the Git repository.
Figure 6-4 Commit, Push, and Pull operation
Let us understand how Git works. You first edit the files in the working tree. After editing the file, you move the file from the working tree to the staging area. Theoption is used to commit the changes from the staging areas to the local repositories. You use the option again to commit changes from the local repository to the Git repository.
You can directly commit the changes from the staging area to the local and Git repository by using theoption.
NOTE:Eclipse supports only EGit and JGit plug-ins.
Perform the following actions to add an existing local Git repository:
Navigate to> > > > .
Figure 6-5 Add an existing local Git repository
Select the required repository and click.
Perform the following actions to clone an existing Git repository:
Navigate to> > > > .
Specify the Git repository URL you wish to clone in the URI field in order to connect it to the local repository. Once the URL is entered, the remaining fields are auto-populated. Enter the Git credentials for authentication.
Figure 6-6 Clone Git Repository
(Optional) Select the branch (if any) in the Branch selection window and click.
By default, a local folder is created with the same repository name. This directory is an editable field. Click.
NOTE:Select theoption to allow the current operation to execute in parallel with other Designer activities.
The cloned repository is now listed under.
Figure 6-7 Cloned repository listed under Git Repositories
In the, right click on the package and select .
Select the; and select if you wish to release the package.
NOTE:Theoption is grayed out when Build to cloned Git repository is selected.
For more information on releasing package, see Releasing and Publishing Packages.
A success message appears. Click.
The built package is listed under.
NOTE:Each time you edit and build the package, a new version of the package is appended to the working tree.
Right click the cloned repository and click. The tab appears.
In thetab, the package is listed under . Right-click on the package and select . The package will be listed under .
NOTE:You must enter a message while committing your changes to the Git repository.
To check-in the changes only to the local repository, click. Click for the changes to be checked-in to both the local and Git repository.
The package is listed in the Git repository.
For more information on publishing the package, see Releasing and Publishing Packages.
Perform the following actions to create a new local Git repository:
Navigate to> > > > .
Specify the directory for the new repository. By default, a local folder is created. This is an editable field and click.
Figure 6-8 Create new local Git repository