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.
...
- Executes native commands using Git client
- Supports partial and shallow checkouts from Git Repository
Instance Properties
Property Name | Required | Description |
|---|
FDGIT_URL
| Yes | The URL to the remote GIT repository. |
FDGIT_USER
| Yes | The username to the remote GIT repository. |
FDGIT_PASSWORD
| Yes | The password for FDGIT_USER. |
FDGIT_CMD_PATH
| No | The GIT executable folder.
Note: If the Git executable is on the PATH, then there is no need to setup this property, otherwise, this needs to be configured on the Environment Instances screen for the workflow instance (different from the 3 above, which are on the SCM Instances screen). |
...
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
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
Image Modified