Setting up the Git integration

To collaborate with other project stakeholders you can open test projects from a local clone of the Git repository, pull project test assets from a Git repository, and push changes made to your local test assets to a Git repository. You can access and use Git from HCL DevOps Test Integrations and APIs (Test Integrations and APIs) and the testing environment is integrated with both local and remote Git repositories.

Installing Git

You must install Git or upgrade the version if you already have installed Git. You can find the instructions to install or upgrade at Installing Git.

Setting up repositories and user identities

After you install Git, you must set up your Git repository and set up access for members. You must ensure that the repository contains your projects and test assets. For more information about Git, see Git.

To set up accounts for users or members, see Account Setup and Configuration for GitHub.

Optionally, you can use a command line utility or Git tool to access the repository, upload your test assets, fetch or pull from the repository, push to the repository, clone the repository, and other operations you want to perform in Git. For more information about how to use Git, see the documentation for your preferred method for accessing and using Git in the Git documentation.

Notes:
  • Users can connect to the remote Git repository by using the SSH keys that are in the user's home directory. You can also set up the user credentials in the Test Integrations and APIs Preferences for Git. See Setting preferences for Git.
  • If you use SSH to connect to your remote repository and Test Integrations and APIs displays an Auth Fail exception while using the deliver changes option, you can resolve this exception by regenerating your SSH keys by using the -m PEM option.
  • In Test Integrations and APIs 9.5.0, for Git Integration with HTTPS connection, you can enable the HTTPS connection by setting the vmarg attribute -Dcom.ibm.jsse2.overrideDefaultTLS=true in the IntegrationTester.ini file or by using the Library Manager. The IntegrationTester.ini file is located in the Test Integrations and APIs installation folder.

Local and shared repositories

After you create a remote or shared repository in Git, you can create a local version of the repository by cloning the remote repository. You must ensure that your projects and test assets are available in the remote repository and are also cloned to the local repository.

Alternatively, if your test project assets are on your local system, you can set up a Git repository in the bare mode, add the project files to the local repository, and then commit and push from the local repository to the remote repository in Git by using your preferred method for doing this.