Refreshing repositories manually

Edit online

You can manually trigger the refresh activity for a repository to instantly fetch and synchronize the changes from the remote repository.

Before you begin

You must have completed the following tasks:

Configured the repository that contains the test assets in your project onIBM® DevOps Test Hub (Test Hub).
Been assigned a Member or a Project Creator role.
Been assigned a Owner role.

About this task

Every two minutes, the repository is refreshed automatically. You can also manually trigger the refresh activity for a repository.

Procedure

Log in to Test Hub and open the team space that contains your project.
Open your project either from the left navigation pane or from the My Projects page.
Click Manage > Configuration from the navigation pane.

The Configuration page of the project is displayed.

In the Repositories section, click the Refresh

icon under Actions column for the repository that you want to update.

The refresh activity is triggered.

Note: The Refresh option is disabled when the refresh is in progress. After the refresh is completed, the Refresh option is enabled.

The following table lists the icons and their description based on the status of the refresh activity:

Refresh icon	Description
	The last refresh activity was successful.
	The last refresh activity was successful but errors were found while processing some of the test assets. To view the error details of the test assets for a specific repository, you can click the arrow inline with the repository name. You can resolve the errors of these test assets in the Git server, and then refresh the server repository, if required. Note: The repository, which contains the branch that is selected in the Branch field, displays the unprocessed test assets for that branch. Other repositories display the unprocessed test assets for their default branch.
	The refresh activity was not successful due to any one of the following reasons: Internal error Connection issue Authentication failure Disk quota exceeded Repository unreachable

Refresh icon

Description

The last refresh activity was successful.

The last refresh activity was successful but errors were found while processing some of the test assets. To view the error details of the test assets for a specific repository, you can click the arrow inline with the repository name.

You can resolve the errors of these test assets in the Git server, and then refresh the server repository, if required.

Note: The repository, which contains the branch that is selected in the Branch field, displays the unprocessed test assets for that branch. Other repositories display the unprocessed test assets for their default branch.

The refresh activity was not successful due to any one of the following reasons:

Internal error
Connection issue
Authentication failure
Disk quota exceeded
Repository unreachable

Results

You have manually refreshed the repository and the Last Refreshed field is updated with the following details:

The time when it was last refreshed in the remote repository.
Latest commit ID and message of the remote repository.