summaryrefslogtreecommitdiffstats
path: root/sonar-core
diff options
context:
space:
mode:
authorMathieu Suen <mathieu.suen@sonarsource.com>2021-06-22 16:06:24 +0200
committersonartech <sonartech@sonarsource.com>2021-06-23 20:03:03 +0000
commit89d54b6b5bfcdddd547c6d379d2bfe3331806a68 (patch)
tree96fdde23f85e734d32282ac347c756d5e20b91da /sonar-core
parent89eba1f0622a489e1e0b92316aaeedbd369c187f (diff)
downloadsonarqube-89d54b6b5bfcdddd547c6d379d2bfe3331806a68.tar.gz
sonarqube-89d54b6b5bfcdddd547c6d379d2bfe3331806a68.zip
SONAR-15068 Adding tooltips for bitbucket DevOps settings
Diffstat (limited to 'sonar-core')
-rw-r--r--sonar-core/src/main/resources/org/sonar/l10n/core.properties6
1 files changed, 5 insertions, 1 deletions
diff --git a/sonar-core/src/main/resources/org/sonar/l10n/core.properties b/sonar-core/src/main/resources/org/sonar/l10n/core.properties
index 91a3164d9c9..f68b0754d62 100644
--- a/sonar-core/src/main/resources/org/sonar/l10n/core.properties
+++ b/sonar-core/src/main/resources/org/sonar/l10n/core.properties
@@ -1132,7 +1132,9 @@ settings.almintegration.form.name.github.help=Give your configuration a clear an
settings.almintegration.form.name.gitlab=Configuration name
settings.almintegration.form.name.gitlab.help=Give your configuration a clear and succinct name. This name will be used at project level to identify the correct configured GitLab instance for a project.
settings.almintegration.form.workspace.bitbucketcloud=Workspace ID
-settings.almintegration.form.workspace.bitbucketcloud.help=The Workspace ID
+settings.almintegration.form.workspace.bitbucketcloud.help=The workspace ID is part of your bitbucket cloud URL {example}
+settings.almintegration.form.oauth_key.bitbucketcloud.help=Bitbucket automatically creates an OAuth key when you create your OAuth consumer. You can find it in your Bitbucket Cloud workspace settings under OAuth consumers.
+settings.almintegration.form.oauth_secret.bitbucketcloud.help=Bitbucket automatically creates an OAuth secret when you create your OAuth consumer. You can find it in your Bitbucket Cloud workspace settings under OAuth consumers.
settings.almintegration.form.url.azure=Azure DevOps URL
settings.almintegration.form.url.azure.help1=For Azure DevOps Server, provide the full collection URL:
settings.almintegration.form.url.azure.help2=For Azure DevOps Services, provide the full organization URL:
@@ -1152,6 +1154,8 @@ settings.almintegration.form.private_key=Private Key
settings.almintegration.form.personal_access_token=Personal Access token
settings.almintegration.form.personal_access_token.azure.help=Token of the user that will be used to decorate the Pull Requests. Needs authorized scope: "Code (read and write)".
settings.almintegration.form.personal_access_token.gitlab.help=Token of the user that will be used to decorate the Merge Requests. Needs API scope authorization.
+settings.almintegration.form.personal_access_token.bitbucket.help=A Bitbucket Server user account is used to decorate Pull Requests. We recommend using a dedicated Bitbucket Server account with Administrator permissions. You need a {pat} from this account with Write permission for the repositories that will be analyzed. This personal access token is used to report the Quality Gate status on your pull requests.
+settings.almintegration.form.personal_access_token.bitbucket.help.url=Personal Access Token
settings.almintegration.form.save=Save configuration
settings.almintegration.form.cancel=Cancel
settings.almintegration.form.secret_field=This field is hidden for security reasons.