Publishing all changes in an Edit branch
After you create or modify any data or test assets in an Edit branch of a project in HCL DevOps Test Hub (Test Hub), you can publish all the changes that are in an Edit branch to the source branch in the project repository. After publishing, other members in the project can view and use the resources.
Before you begin
- Ensured that you are assigned a role as a Project Owner or Tester in the project. See Managing access to the server projects.
- Created or modified a test or data asset.
- Read and understood the information in Edit branch overview and Create or select an Edit branch.
About this task
When you create or modify multiple assets in a project, the Changes page lists all the changed assets in the selected branch. In this scenario, you cannot publish or discard a single change. You must either publish or discard all changes that are made to all the listed assets. The Changes page also provides you with information about the number of commits that the selected branch is ahead and behind. After you publish an asset to the Git repository, all the other project members who have access to that asset can view the updated asset. You can perform the following actions in the Changes page:
| Options | Actions |
|---|---|
| Edit | Click Edit to make any updates to the asset before publishing. |
| Discard | Click Discard to remove the changes that you made to the asset. |
| Save as | Click Save as to save a copy of the
asset. Note:
When you try to publish a modified asset with conflicting edits, an error about conflicting changes is displayed. However, you can use the Save as option to save a copy of the asset edits under a new asset name. You must discard the edits that you made to the original asset. For example, consider a scenario when Amy Smith and John Doe edit the same Data definition, and Amy Smith edits and publishes the Data definition. On the Changes page, a message that indicates the number of commits ahead and behind in the branch is displayed when John Doe tries to publish the same Data definition. You can then use the Save as option to resolve this issue. |
| Update | Click Update to merge the changes from remote branch that are not in your Edit branch. |
| Details | Click Details to see the changes. |
| Reset | Click Reset to rever the change. |
| Push | Click Push to upload the edit branch to remote repository when a conflict prevents publishing. |
Procedure
-
Log in to Test Hub.
The Projects page of the initial team space is displayed.
-
Click to open the project that contains the test assets.
The Overview page of the project is displayed.
- Go to .
-
Select the required branch from the Branch list.
All the updated assets that are present in the selected branch are displayed in the Changes page.
-
Click Publish.
The Publish dialog is displayed.
-
Enter a description for the changes that you performed to the asset, and then
click Publish.
If the publish succeeds, the Edit branch is automatically deleted and removed from the Branch list and the changes are merged into the previously selected remote branch.If the publish fails due to a conflict with the remote branch, click Push in the Publish dialog to push the edit branch to the remote repository. Then, you can create a pull request and resolve the conflicts manually in Git before you merge the changes into the target branch.