Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
Y
YeeAmosFireAutoSysRoot
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
station
YeeAmosFireAutoSysRoot
Commits
5f459a20
Commit
5f459a20
authored
Feb 23, 2023
by
suhuiguang
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
1.ci分析
parent
8e6ae18a
Pipeline
#253
passed with stage
in 7 minutes 38 seconds
Changes
2
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
29 additions
and
0 deletions
+29
-0
.gitlab-ci.yml
.gitlab-ci.yml
+17
-0
sonar-project.properties
sonar-project.properties
+12
-0
No files found.
.gitlab-ci.yml
0 → 100644
View file @
5f459a20
sonarqube-check-autosys
:
image
:
name
:
sonarsource/sonar-scanner-cli:latest
entrypoint
:
[
"
"
]
variables
:
SONAR_USER_HOME
:
"
${CI_PROJECT_DIR}/.sonar"
# Defines the location of the analysis task cache
GIT_DEPTH
:
"
0"
# Tells git to fetch all the branches of the project, required by the analysis task
cache
:
key
:
"
${CI_JOB_NAME}"
paths
:
-
.sonar/cache
script
:
-
sonar-scanner -Dsonar.qualitygate.wait=true
allow_failure
:
true
only
:
-
main
\ No newline at end of file
sonar-project.properties
0 → 100644
View file @
5f459a20
sonar.projectKey
=
YeeAmosFireAutoSysRoot
sonar.projectName
=
YeeAmosFireAutoSysRoot
sonar.projectVersion
=
1.0.0.0
sonar.sources
=
.
sonar.exclusions
=
sonar.sourceEncoding
=
UTF-8
sonar.java.binaries
=
.
sonar.language
=
java
sonar.login
=
admin
sonar.password
=
sonar123
sonar.java.source
=
1.8
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment