# Git Server Git server is a centralized platform for hosting Git repositories, facilitating version control and collaboration in software development projects. The IT-Conductor Git Adapter enables seamless integration and synchronization across diverse Git servers, including GitHub, GitLab, BitBucket, Azure DevOps, and self-hosted options. Software development teams use various Git platforms depending on their project requirements and preferences. ### **Configure Git Server in IT-Conductor** To configure a git server in IT-Conductor, follow the instructions below. #### **Add New Git Server** 1. Visit [service.itconductor.com](https://service.itconductor.com/) and enter your login credentials. 2. Navigate to **Dashboards → Administrator** to access the **Administrator's Dashboard**. 3. Locate the **Git Servers** actions panel and click the title to access the complete list.

Figure 1: Git Servers Actions Panel in Administrator's Dashboard

4. Click **Create New Github Connection**

or **Create New Git Connection**

Figure 2: Git Servers Actions Panel Page

**Add New GitHub Connection** 1. Fill out all the necessary information in the **New Github Instance** wizard. Once completed, click

to add the system.

Figure 3a: New GitHub Instance Wizard (New Git Server Screen)

* **Description** - refers to any relevant information about the git server being added. * **Organization** - refers to an administrative structure that defines objects with a common goal or purpose. If you previously created an organization, please select it. * **Role** - refers to the environment where the git server will be used. * **Site** - refers to a logical object that describes a particular area or location, depending on the context in which it is used. * **Gateway** - allows communication between the customer's site network and the IT-Conductor cloud platform. Select the previously configured gateway from the dropdown menu. See [Gateway Setup](https://docs.itconductor.com/user-guide/setup/gateway-setup) for more details. * **Host** - refers to the type of git server that will be added to IT-Conductor. By default, it's github.com. 2. Provide the account information in the **New Account** screen and click

to complete the configuration.

Figure 3b: New GitHub Instance Wizard (New Account Screen)

* **Description** - refers to any relevant information about the GitHub account being added. * **Person** - refers to the user who's creating the GitHub instance. * **User Name** - refers to a unique token generated on GitHub. For more information on generating a token, please refer to this [documentation on managing personal access tokens on Git Hub.](https://docs.github.com/en/enterprise-server@3.9/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens) * **Token** - allows IT-Conductor to use a GitHub-generated token instead of a username and password. {% hint style="info" %} **Note:** When configuring GitHub access, please use the GitHub-generated **Access Token** as the user name (the password field should be blank). {% endhint %} 4. Verify if the server was added to the **Git Servers** actions panel and check its status. **Add New Git Connection** 1. Fill out all the necessary information in the **New Git Instance** wizard. Once completed, click

to add the system.

Figure 4a: New Git Instance Wizard (New Git Server Screen)

* **Description** - refers to any relevant information about the git server being added. * **Organization** - refers to an administrative structure that defines objects with a common goal or purpose. If you previously created an organization, please select it. * **Role** - refers to the environment where the git server will be used. * **Site** - refers to a logical object that describes a particular area or location, depending on the context in which it is used. * **Gateway** - allows communication between the customer's site network and the IT-Conductor cloud platform. Select the previously configured gateway from the dropdown menu. See [Gateway Setup](https://docs.itconductor.com/user-guide/setup/gateway-setup) for more details. * **Protocol** - refers to the communication protocol (HTTPS by default) that will be used to access the git server. * **Host** - refers to the type of git server that will be added to IT-Conductor. It can be GitHub, GitLab, BitBucket, or Azure DevOps. 2. Provide the account information in the **New Account** screen and click

to complete the configuration.

Figure 4b: New Git Instance Wizard (New Account Screen)

* **Description -** short description of the user. * **Application** - refers to the type of git server added in step 1. * **Person** - refers to the user who's creating the Git instance. * **User name** - unique token generated on GitHub. For more information on generating a token, please refer to this [documentation on managing personal access tokens on Git Hub.](https://docs.github.com/en/enterprise-server@3.9/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens) * **Token** - this field allows IT-Conductor to use a GitHub-generated token instead of a username and password. {% hint style="info" %} **Note:** When configuring GitHub access, please use the GitHub-generated **Access Token** as the user name (the password field should be blank). {% endhint %} 4. Verify if the newly added connection was added to the **Git Servers** actions panel and check its status. {% hint style="info" %} **Note for Git and Github connections:** The status will remain on **Ready** for a few minutes. Refresh the panel if needed. If there are configuration issues, such as incorrect connection parameters or an invalid account, the status will remain on **Ready**. Click on the negative space to trigger the pop-up menu and click on the **Log** icon ![](https://docs.itconductor.com/~gitbook/image?url=https:%2F%2F377464071-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXhp08OmU8050PePmMgDt%252Fuploads%252FGx0Q4OSu3wOOo5O8ZbQC%252Flog.gif%3Falt=media%26token=55a3b985-c68a-4120-a285-2afac310a988\&width=42\&dpr=4\&quality=100\&sign=c722a48497f25a2090f362f749f70677b04e8ad6a14fbfe2efcbe21458940d70) to display the logs and troubleshoot. If everything is configured correctly, the status will change to **In Progress.** {% endhint %} 5. Navigate to the service grid and verify if the system was added under the **Git Servers** node**.** {% hint style="info" %} **Note:** The server will appear in the service grid within 5-15 minutes. {% endhint %}