The FlexDeploy Git plugin makes it easy to interact with source code stored in a Git repository. This plugin requires a Git client to be stored on the FlexDeploy server and any endpoints which will execute Git plugin operations. FlexDeploy allows users to configure Git repository connection details to be shared by various projects and other configurations at a project level.  This allows workflows to perform clone and tag operations within a workflow.

• Create SCM Instance for Git and define URL, User and Password information. You can also validate connection when creating SCM Instance for Git.

• At project level, select Git as SCM Type and provide details like Branch, Sparse Folders, Tag etc. which are defined as Groovy scripts.

Supported Versions

• 1.7.9+

Key Features

• Executes native commands using Git client

• Supports partial and shallow checkouts from Git Repository

Integration Properties

Target Properties

Plugin Operations

Git Installation Steps

Git 1.7.9 or higher is needed for FlexDeploy. If yum installs a lower version by default, then you need to get the Git source code and build it for install. Here is reference - https://tecadmin.net/install-git-2-0-on-centos-rhel-fedora/.

Run these steps as root. You can download a newer version than 2.7.1 as well.

1. yes | yum install curl-devel expat-devel gettext-devel openssl-devel zlib-devel

2. yes | yum install gcc perl-ExtUtils-MakeMaker

3. cd $HOME

4. wget https://github.com/git/git/archive/v2.7.1.tar.gz

5. tar -xvzf v2.7.1.tar.gz

6. cd git-2.7.1/

7. make prefix=/usr/local all

8. make prefix=/usr/local install

Token authentication is required for GIT operations

Personal access tokens (PATs) are an alternative to using passwords for authentication to GitHub when using the GitHub API or the command line. 

To create a Personal access token, follow the below link

https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token

While generating Key Scope items is completely based on your requirement.

Basic permission to grant this token is required, Repo- Full control of private repositories

Admin:repo_hook- read:repo_hook read repository hooks for a clone, if you are doing commit from FlexDeploy then you need write:repo_hook

After generates token, In FlexDeploy, Update GIT password with the token at GIT Instance under Topology - Integrations - Source control tab

Open

Multiple SSH Keys for different repositories

If you have more than one source control account with the same domain name (i.e. github.com, bitbucket.org, etc) and wish to use a different SSH key for each account follow the below instructions:

1. Generate your SSH keys if you have don’t have them already. SSH key must be RSA algorithm (ssh-keygen -t rsa). It’s recommended to store the SSH keys in the .ssh folder.

2. Ensure <FlexDeploy_User_Home/.ssh folder exists. The .ssh folder should already be there in the home directory since ~/.ssh directory is automatically created when the user runs the ssh command for the first time. If the directory doesn’t exist on your system, create it using the command below:

   mkdir -p ~/.ssh && chmod 700 ~/.ssh

3. Create the configuration file name “config” in the <FlexDeploy_User_Home>/.ssh/ directory of the user running FlexDeploy, if it doesn’t already exist.

   • The SSH config file takes the following structure:

     Host hostname1 SSH_OPTION value SSH_OPTION value Host hostname2 SSH_OPTION value Host * SSH_OPTION value

   • Add the appropriate entries for your organization and use case. In this example, we’ll add one entry with Host “bitbucket-alt”

     Host bitbucket-alt HostName bitbucket.org IdentityFile ~/.ssh/<your_SSH_key> IdentitiesOnly yes

4. On the account instance, set Host value in the URL.

I.E. ssh://git@bitbucket-alt/flexagon/dummy-repo.git

Effectively, you can use alternate SSH key for any SCM account by changing the URL.