Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This documentation consists of the Global Configurations available in Devtron.
Parts of the Documentation
Devtron uses GitOps and stores configurations in git; Git Credentials can be entered at Global Configuration > GitOps
which is used by Devtron for configuration management and storing desired state of the application configuration. In case GitOps is not configured, Devtron cannot deploy any application or charts.
Areas impacted by GitOps are:
Deployment Template, click here to learn more.
Charts, click here to learn more.
Select the GitOps section of global configuration. At the top of the section, four Git providers are available.
GitHub
GitLab
Azure
BitBucket Cloud
Select one of the Git providers. To add git account, You need to provide the following inputs as given below:
Git Host / Azure DevOps Organisation Url / BitBucket Host
GitHub Organization Name / Gitlab Group id / Azure DevOps Project Name / BitBucket Workspace ID
BitBucket Project Key (only for BitBucket Cloud)
Git access credential
This field is filled by default, Showing the URL of the selected git providers. For example- https://github.com for GitHub, https://gitlab.com for GitLab, https://dev.azure.com/ for Azure & https://bitbucket.org for BitBucket. Please replace them(not available for GitHub & BitBucket) if they are not the url you want to use.
In the case of GitHub provide Github Organization Name*
. Learn more about Github organization Name.
In the case of Gitlab provide Gitlab group Id*
. Learn more about Gitlab group Id.
Similarly in the case of Azure provide Azure DevOps Project Name*
. Learn more about Azure DevOps Project Name.
For Bitbucket Cloud, provide Bitbucket Workspace Id*
. Learn more about Bitbucket Workspace Id.
This field is non-mandatory and is only to be filled when you have chosen Bitbucket Cloud
as your git provider. If not provided, the oldest project in the workspace will be used. Learn more about Bitbucket Project Key.
Provide Git Username
and Personal Access Token
of your git account.
(a) Username Username for your git account.
(b) Personal Access Token A personal access token (PAT) is used as an alternate password to authenticate into your git accounts.
repo - Full control of private repositories(Access commit status , Access deployment status and Access public repositories).
admin:org - Full control of organizations and teams(Read and write access).
delete_repo - Grants delete repo access on private repositories.
api - Grants complete read/write access to the scoped project API.
write_repository - Allows read-write access (pull, push) to the repository.
code - Grants the ability to read source code and metadata about commits, change sets, branches, and other version control artifacts. More Information on scopes in Azure devops.
repo - Full control of repositories (Read, Write, Admin, Delete access).
Click on Save to save your gitOps configuration details.
Note: A Green tick will appear on the active gitOps provider.
Git Accounts allow you to connect your code source with Devtron. You will be able to use these git accounts to build the code using the CI pipeline.
Global Configuration
helps you to add a Git provider. Click on Add git account
button at the top of the Git Account Section. To add a new git provider, add the details as mentioned below.
Name
Git Host
URL
Authentication type
Provide a Name
to your Git provider. This name will be displayed in the the Git Provider drop-down inside the Git Material configuration section.
It is the git provider on which corresponding application git repository is hosted. By default you will get Bitbucket and GitHub but you can add many as you want clicking on [+ Add Git Host].
Here provide the type of authentication required by your version controller. Devtron supports three types of authentications. You can choose the one that suits you the best.
Anonymous
If authentication type is set as Anonymous
then you do not need to provide any username, password/authentication token or SSH key. Just click on Save
to save the git account provider details.
If authentication type is set as
Anonymous
, only public git repository will be accessible.
User Auth
If you select User Auth
then you have to provide the Username
and either of Password
or Auth Token
for the authentication of your version controller account. Click on Save
to save the git account provider details.
SSH Key
If you choose SSH Key
then you have to provide the Private SSH Key
corresponding to the public key added in your version controller account. Click on Save
to save the git account provider details.
You can update your saved git account settings at anytime. To update the git account:
Click on the git account which you want to update.
Make the required changes
Click on Update
to save the changes.
Updates can only be made within one Authentication type or one protocol type, i.e. HTTPS(Anonymous or User Auth) & SSH. You can update from Anonymous to User Auth & vice versa, but not from Anonymous/User Auth to SSH or reverse.
Disabled git accounts will be unavailable for use in future applications. Applications already using a disabled git account will not be affected.
Provide the URL
. For example- for Github, for GitLab, etc.
You can enable or disable a git account. Enabled git accounts will be available to be used in Application configuration > .