About Git Repository Linkage
- 17 Jul 2024
- Print
- PDF
About Git Repository Linkage
- Updated on 17 Jul 2024
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
summary
Git repository linkage outputs transfer settings and data mart definition configuration information in YAML format, which can be reflected in a specified Git repository.
This page describes how to set up and use Git repository integration.
Plan Restrictions
Git repository integration is only available for accounts subscribed to the Advanced plan or higher.
Hosting services supported by this function
Git repository integration supports major hosting services for Git repositories.
The following are examples of supported hosting services.
- GitHub
- GitLab
- Git functionality in Backlog
Git repository integration is also available for on-premise environments using GitHub Enterprise, etc.
Reflected object
- Configuration information for forwarding settings
- Configuration information for data mart definitions
Cooperation type
There are two types of linkage types for Git repository linkage: user and****resource group.
You can link one Git repository to your account or to each resource group.
Linkage type: User
About the linkage type "User"
This is a linkage setting for TROCCO users.
For the following resources (transfer settings and data mart definitions), all operations related to Git repository integration settings are available.
* Resources created by you
* Resources that do not belong to a resource group
Collaboration type: Resource Group
role permission
The operations allowed depend on the type of role the resource group has granted to the team to which it belongs.
See Resource Groups for more information on each role in a resource group.
The operations allowed for each role are as follows
| Resource Group Administrator | Resource Group Editor | Resource Group Operator | Resource Group Viewer | No Role | |
|---|---|---|---|---|---|
| Creating and Editing Git Repository Linkage Settings | ✓ | ✓ | ✓ | - | - |
| Check diff with Git | ✓ | ✓ | ✓ | - | - |
| commit/push to Git | ✓ | ✓ | ✓ | - | - |
| Displaying Linked Information | ✓ | ✓ | ✓ | ✓ | ✓ |
Below is an example of a user's Git repository integration screen.
* For the resource group "test_1", the user is granted the resource group administrator or resource group editor role.
* For resource groups "test_2" and "test_3", the user is granted the resource group operator or resource group viewer role.
Resource group not displayed on the Git repository integration screen
Resource groups that do not have roles assigned to the team to which you belong and for which you are not the creator will not appear on the Git repository integration screen.
Remote Repository Settings
On the Git Repository Linkage screen, click Create New.
Enter the repository URL of the Git server and click Link.
Request for permission of IP address
If you are using GitHub Enterprise or other means to deny access to your Git server from any IP address other than the specific IP address, please allow access to the IP address that TROCCO uses for communication.
IP addresses that need to be allowed by security groups, firewalls, etc.
- Specify a branch name, register the Deploy Key with the Git server, confirm the connection, and click Save.
Diff (diff) check
You can view diffs from the Git repository below.
* From the Git repository linkage list screen, click Check All Differences.
* Click " Reflect in Git (to confirmation screen) " on the detail screen of each transfer setting and the detail screen of each data mart definition.
Reflect to Git repository (git commit & push)
On the diff confirmation screen, click Reflect in Git.
Enter the Commit Title and Commit Details and click Reflect in Git Repository.
The configuration information in YAML format is reflected in the target Git repository.
Was this article helpful?