diff options
author | Wouter Admiraal <wouter.admiraal@sonarsource.com> | 2020-04-21 17:42:30 +0200 |
---|---|---|
committer | sonartech <sonartech@sonarsource.com> | 2020-05-04 20:03:53 +0000 |
commit | b7d68dca795cf2127efbaa8b5c2cba0ee32192ee (patch) | |
tree | f33a9307a7b07f0077782a10887e4a5699d714d7 /sonar-core | |
parent | 1d854eec0d3e223aee54412503fcccf50ee10f4a (diff) | |
download | sonarqube-b7d68dca795cf2127efbaa8b5c2cba0ee32192ee.tar.gz sonarqube-b7d68dca795cf2127efbaa8b5c2cba0ee32192ee.zip |
SONAR-13296 Add new Jenkins tutorial for Bitbucket Server
Diffstat (limited to 'sonar-core')
-rw-r--r-- | sonar-core/src/main/resources/org/sonar/l10n/core.properties | 99 |
1 files changed, 99 insertions, 0 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 d111d22a497..d13c038a540 100644 --- a/sonar-core/src/main/resources/org/sonar/l10n/core.properties +++ b/sonar-core/src/main/resources/org/sonar/l10n/core.properties @@ -3180,6 +3180,7 @@ onboarding.build=What is your build technology? onboarding.build.maven=Maven onboarding.build.gradle=Gradle onboarding.build.make=Make +onboarding.build.msbuild=MSBuild onboarding.build.other=Other (for JS, TS, Go, Python, PHP, ...) onboarding.language=What is your project's main language? @@ -3252,6 +3253,104 @@ onboarding.analysis.sqscanner.docs.gradle.example_project.title=live Gradle-base onboarding.tutorial.return_to_list=Choose another option +onboarding.tutorial.choose_method=How do you want to analyze your repository? +onboarding.tutorial.choose_method.manual=Manually +onboarding.tutorial.choose_method.jenkins=With Jenkins + +onboarding.tutorial.with.jenkins.title=Analyze your project with Jenkins +onboarding.tutorial.with.jenkins.only_bitbucket=This tutorial is only available for projects bound to Bitbucket Server. +onboarding.tutorial.with.jenkins.prereqs.title=Prerequisites +onboarding.tutorial.with.jenkins.prereqs.intro.sentence=To run your project analyses with Jenkins, the following plugins {must_have} +onboarding.tutorial.with.jenkins.prereqs.intro.sentence.must_have=must be installed and configured: +onboarding.tutorial.with.jenkins.prereqs.plugins.branch_source=Bitbucket Branch Source plugin for Jenkins - version 2.7 or later +onboarding.tutorial.with.jenkins.prereqs.plugins.sonar_scanner=SonarQube Scanner plugin for Jenkins - version 2.11 or later +onboarding.tutorial.with.jenkins.prereqs.step_by_step_guide=For a step by step guide on installing and configuring those plugins in Jenkins, visit the {link} documentation page. +onboarding.tutorial.with.jenkins.prereqs.step_by_step_guide.link=Analysis Prerequisites +onboarding.tutorial.with.jenkins.prereqs.following_are_recommendations=We recommend using the configuration in the following steps for the best results, but you can customize it as needed. +onboarding.tutorial.with.jenkins.prereqs.done=Configure Analysis +onboarding.tutorial.with.jenkins.multi_branch_pipeline.title=Create a Multibranch Pipeline Job +onboarding.tutorial.with.jenkins.multi_branch_pipeline.intro=Create a Multibranch Pipeline in order to automatically analyze all your branches and pull requests. +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step1.sentence=From Jenkins' dashboard, click {new_item} and create a {type}. +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step1.sentence.new_item=New Item +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step1.sentence.type=Multibranch Pipeline Job +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step2.sentence=Under {tab}, add a Bitbucket source and enter the following information: +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step2.sentence.tab=Branch Sources +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step2.server.label=Server +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step2.server.action=select the instance hosting the repository you want to analyze. +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step2.creds.label=Credentials +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step2.creds.action=select the Bitbucket Server credentials. +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step2.owner.label=Owner +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step2.owner.action=enter your project key. +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step2.repo.label=Repository +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step2.repo.action=select the repository you want to analyze. +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step2.behaviour.label=Behavior +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step2.behaviour.action=select Exclude branches that are also filed as PRs. +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step3.sentence=Jump to the {tab} section and set the following parameters: +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step3.sentence.tab=Build Configuration +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step3.mode.label=Mode +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step3.mode.action=by Jenkinsfile +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step3.script_path.label=Script Path +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step3.script_path.action=Jenkinsfile +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step4.sentence=Click {save}. +onboarding.tutorial.with.jenkins.multi_branch_pipeline.step4.sentence.save=Save +onboarding.tutorial.with.jenkins.bitbucket_webhook.title=Create a Bitbucket Server Webhook +onboarding.tutorial.with.jenkins.bitbucket_webhook.intro.sentence=Create a Webhook in your repository to trigger the Jenkins job on push. Already have a Webhook configured? {link} +onboarding.tutorial.with.jenkins.bitbucket_webhook.intro.link=Skip this step. +onboarding.tutorial.with.jenkins.bitbucket_webhook.step1.sentence=Go to the {link} and enter the following information: +onboarding.tutorial.with.jenkins.bitbucket_webhook.step1.link=Bitbucket Server Webhook creation page for your repository +onboarding.tutorial.with.jenkins.bitbucket_webhook.step1.name.label=Name +onboarding.tutorial.with.jenkins.bitbucket_webhook.step1.name.action=give a unique name. +onboarding.tutorial.with.jenkins.bitbucket_webhook.step1.url.label=URL +onboarding.tutorial.with.jenkins.bitbucket_webhook.step1.url.action=Enter the following URL, replacing the tokens as needed: +onboarding.tutorial.with.jenkins.bitbucket_webhook.step1.url.warning=The Bitbucket Server URL must be identical to the one in your Jenkins configuration. Watch out for any missing or extra "/" at the end. +onboarding.tutorial.with.jenkins.bitbucket_webhook.step2.sentence=Under {events}, make sure the following options are checked: +onboarding.tutorial.with.jenkins.bitbucket_webhook.step2.sentence.events=Events +onboarding.tutorial.with.jenkins.bitbucket_webhook.step2.repo.label=Repository +onboarding.tutorial.with.jenkins.bitbucket_webhook.step2.repo.action=Push +onboarding.tutorial.with.jenkins.bitbucket_webhook.step2.pr.label=Pull Request +onboarding.tutorial.with.jenkins.bitbucket_webhook.step2.pr.action=Opened +onboarding.tutorial.with.jenkins.bitbucket_webhook.step3.sentence=Click {create}. +onboarding.tutorial.with.jenkins.bitbucket_webhook.step3.sentence.create=Create +onboarding.tutorial.with.jenkins.jenkinsfile.title=Create a Jenkinsfile +onboarding.tutorial.with.jenkins.jenkinsfile.jenkinsfile_step.sentence=Create a {file} file in your repository and paste the following code: +onboarding.tutorial.with.jenkins.jenkinsfile.maven.step2.sentence=Add the following to your {file} file: +onboarding.tutorial.with.jenkins.jenkinsfile.maven.step3.replace.sentence=Make sure to replace {default} with the name you gave to your Maven tool {in_jenkins}. +onboarding.tutorial.with.jenkins.jenkinsfile.maven.step3.replace.sentence.default=Default Maven +onboarding.tutorial.with.jenkins.jenkinsfile.maven.step3.replace.sentence.in_jenkins=in Jenkins +onboarding.tutorial.with.jenkins.jenkinsfile.maven.step3.help1.sentence=To get the name of your Maven tool in Jenkins, navigate to {path}. +onboarding.tutorial.with.jenkins.jenkinsfile.maven.step3.help1.sentence.path=Manage Jenkins > Global Tool Configuration +onboarding.tutorial.with.jenkins.jenkinsfile.maven.step3.help2.sentence=The name is located under the {path} section, in the {name} field. +onboarding.tutorial.with.jenkins.jenkinsfile.maven.step3.help2.sentence.path=Maven > Maven installations +onboarding.tutorial.with.jenkins.jenkinsfile.maven.step3.help2.sentence.name=Name +onboarding.tutorial.with.jenkins.jenkinsfile.gradle.step2.sentence=Add the following to your {file} file: +onboarding.tutorial.with.jenkins.jenkinsfile.msbuild.step2.replace.sentence=Make sure to replace {default_msbuild} and {default_scanner} with the names you gave to your MSBuild and SonarScanner for MSBuild tools {in_jenkins}. +onboarding.tutorial.with.jenkins.jenkinsfile.msbuild.step2.replace.sentence.default_msbuild=Default MSBuild +onboarding.tutorial.with.jenkins.jenkinsfile.msbuild.step2.replace.sentence.default_scanner=SonarScanner for MSBuild +onboarding.tutorial.with.jenkins.jenkinsfile.msbuild.step2.replace.sentence.in_jenkins=in Jenkins +onboarding.tutorial.with.jenkins.jenkinsfile.msbuild.step2.help1.sentence=To get the name of these tools in Jenkins, navigate to {path}. +onboarding.tutorial.with.jenkins.jenkinsfile.msbuild.step2.help1.sentence.path=Manage Jenkins > Global Tool Configuration +onboarding.tutorial.with.jenkins.jenkinsfile.msbuild.step2.help2.sentence=For your MSBuild tool, the name is located under the {path} section, in the {name} field. +onboarding.tutorial.with.jenkins.jenkinsfile.msbuild.step2.help2.sentence.path=MSBuild > MSBuild installations +onboarding.tutorial.with.jenkins.jenkinsfile.msbuild.step2.help2.sentence.name=Name +onboarding.tutorial.with.jenkins.jenkinsfile.msbuild.step2.help3.sentence=For your SonarScanner for MSBuild tool, the name is located under the {path} section, in the {name} field. +onboarding.tutorial.with.jenkins.jenkinsfile.msbuild.step2.help3.sentence.path=SonarScanner for MSBuild > SonarScanner for MSBuild installations +onboarding.tutorial.with.jenkins.jenkinsfile.msbuild.step2.help3.sentence.name=Name +onboarding.tutorial.with.jenkins.jenkinsfile.other.step2.sentence=Create a {file} file in your repository and paste the following code: +onboarding.tutorial.with.jenkins.jenkinsfile.other.step3.replace.sentence=Make sure to replace {default} with the name you gave to your SonarQube Scanner tool {in_jenkins}. +onboarding.tutorial.with.jenkins.jenkinsfile.other.step3.replace.sentence.default=SonarScanner +onboarding.tutorial.with.jenkins.jenkinsfile.other.step3.replace.sentence.in_jenkins=in Jenkins +onboarding.tutorial.with.jenkins.jenkinsfile.other.step3.help1.sentence=To get the name of your SonarQube Scanner tool in Jenkins, navigate to {path}. +onboarding.tutorial.with.jenkins.jenkinsfile.other.step3.help1.sentence.path=Manage Jenkins > Global Tool Configuration +onboarding.tutorial.with.jenkins.jenkinsfile.other.step3.help2.sentence=The name is located under the {path} section, in the {name} field. +onboarding.tutorial.with.jenkins.jenkinsfile.other.step3.help2.sentence.path=SonarQube Scanner > SonarQube Scanner installations +onboarding.tutorial.with.jenkins.jenkinsfile.other.step3.help2.sentence.name=Name +onboarding.tutorial.with.jenkins.all_set.sentence={all_set} and ready to improve the quality and security of your code! +onboarding.tutorial.with.jenkins.all_set.sentence.all_set=You're all set +onboarding.tutorial.with.jenkins.commit=Commit and push your code to start the analysis. +onboarding.tutorial.with.jenkins.commit.why=Each new push you make on your branches or pull requests will trigger a new analysis in SonarQube. +onboarding.tutorial.with.jenkins.refresh=This page will then refresh with your analysis results. +onboarding.tutorial.with.jenkins.refresh.why=If the page doesn't refresh after a while, please double-check the analysis configuration. + #------------------------------------------------------------------------------ # # BRANCHES |