更新.gitlab-ci.yml文件

.gitlab-ci.yml

-# This file is a template, and might need editing before it works on your project.
-# To contribute improvements to CI/CD templates, please follow the Development guide at:
-# https://docs.gitlab.com/ee/development/cicd/templates.html
-# This specific template is located at:
-# https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Getting-Started.gitlab-ci.yml
-
-# This is a sample GitLab CI/CD configuration file that should run without any modifications.
-# It demonstrates a basic 3 stage CI/CD pipeline. Instead of real tests or scripts,
-# it uses echo commands to simulate the pipeline execution.
-#
-# A pipeline is composed of independent jobs that run scripts, grouped into stages.
-# Stages run in sequential order, but jobs within stages run in parallel.
-#
-# For more information, see: https://docs.gitlab.com/ee/ci/yaml/index.html#stages
-
-stages:          # List of stages for jobs, and their order of execution
-  - build
-  - test
-  - deploy
-
-build-job:       # This job runs in the build stage, which runs first.
-  stage: build
-  script:
-    - echo "Compiling the code..."
-    - echo "Compile complete."
-
-unit-test-job:   # This job runs in the test stage.
-  stage: test    # It only starts when the job in the build stage completes successfully.
-  script:
-    - echo "Running unit tests... This will take about 60 seconds."
-    - sleep 60
-    - echo "Code coverage is 90%"
-
-lint-test-job:   # This job also runs in the test stage.
-  stage: test    # It can run at the same time as unit-test-job (in parallel).
-  script:
-    - echo "Linting code... This will take about 10 seconds."
-    - sleep 10
-    - echo "No lint issues found."
-
-deploy-job:      # This job runs in the deploy stage.
-  stage: deploy  # It only runs when *both* jobs in the test stage complete successfully.
-  script:
-    - echo "Deploying application..."
-    - echo "Application successfully deployed."
+stages:
+  - sca
+#定义管道中的阶段
+sca:
+  stage: sca
+  image: "repo.gitsec.cn/docker/sca_scanner:latest"
+  #选择使用那个镜像
+  tags:
+    - k8s
+  script:
+    -  java -jar /opt/seczone/scanner.jar --filePath /builds/Hozenri/renren-srcurity --parseFrom 4 --cliMode portal --projectName test_cli_portal2 --phase Phase_1 --onCache true --mergeMode FULL --retrunCheckReport true --token c291cmNlLWFwaUBzZWN6b25lLmNuOmNmYTcxYTUyNjFjZTQ3NmM5MGNhNDRjNmIyNGNiNGM3 --portalIp https://sca.gitsec.cn/
+#需要修改的值，token如果失效需要找管理员申请，portalIp为工具地址（该字段不用修改），filePath检测的文件目录，在k8s中为/builds/gitlab用户名/项目名称（例如“/builds/admin/MCMS”） groupName不用修改，projectName，项目名称修改成你想要的名称防止名称重复导致失败
+#修改参数示例，token，在上述脚本中其中一段为“--token ********”修改只需要修改--token空格后的内容即可其他参数同理，可以允许不同应用相同项目名
+    - ls;pwd
+  artifacts:
+    reports: 
+      dependency_scanning: vulReport.json
+      license_scanning: licenseReport.json
+    paths:
+      - licenseReport.json
+      - vulReport.json
+#读取检测结果不用修改
+    expire_in: 3 day
\ No newline at end of file