While FlexDeploy supports a half dozen Source Control Management system types, blueprints currently manage the most popular ones.
The Blueprint will collect the information required to create the connection. In addition, the project's source details will be configured with SCM specifc properties.
For Subversion, the Trunk Path defines the location within the repository that contains the "trunk" branch for the project's source.
For Git, the Sparse Checkout Folder defines the sub-tree of the repository which contains the project's source.
For Microsoft TFS, the Main Script defines the location under the collection which contains the project's source.
Git Discovery
Specific for Git, there is the option to directly connect to a provider to more easily define a source control connection with FlexDeploy.
...
Working with Git
When choosing Git as your Source Control System you get the option to link directly to your GitHub, Bitbucket, GitLab, or Azure DevOps account which allows easier configuration when running through Blueprints.
You are first prompted for your provider and credentials.
| Info | ||
|---|---|---|
| ||
You can both remember your provider selection and remember credentials.
Both of these settings can also be set/cleared from the preferences menu |
Next you can select the repository you want to use from your account:
Finally you can select an optional Sparse Checkout Folder if needed:
Preferences
In the preferences menu you can select things like default Source Control configuration or themes! (Access from options drop down on the top right).
