As we reevaluate how to best support and maintain Staging Ref in the future, we encourage development teams using this environment to highlight their use cases in the following issue: https://gitlab.com/gitlab-com/gl-infra/software-delivery/framework/software-delivery-framework-issue-tracker/-/issues/36.

Skip to content
Snippets Groups Projects
Unverified Commit f8880e60 authored by Igor Drozdov's avatar Igor Drozdov
Browse files

Restructure CI jobs

- Introduce lint and post-test stages
- Move all lint related jobs to the lint stage
- Move all post-test related jobs to the post-test stage
parent c5d0726f
No related branches found
No related tags found
No related merge requests found
Loading
Loading
@@ -7,7 +7,9 @@ include:
stages:
- prepare
- lint
- test
- post-test
variables:
FF_USE_FASTZIP: 'true'
Loading
Loading
@@ -174,10 +176,12 @@ race:
- make test_golang_race
code_quality:
stage: lint
extends: .use-docker-in-docker
rules: *workflow_rules
code_navigation:
stage: post-test
image: sourcegraph/lsif-go:v1.9
allow_failure: true
script:
Loading
Loading
@@ -188,17 +192,21 @@ code_navigation:
# SAST
semgrep-sast:
stage: lint
rules: *workflow_rules
# Dependency Scanning
gemnasium-dependency_scanning:
stage: lint
rules: *workflow_rules
# Secret Detection
secret_detection:
stage: lint
rules: *workflow_rules
build-package-and-qa:
stage: post-test
trigger:
project: 'gitlab-org/build/omnibus-gitlab-mirror'
branch: 'master'
Loading
Loading
@@ -230,13 +238,14 @@ build-package-and-qa:
needs: []
modules:tidy:
stage: lint
needs: ['modules:download']
script:
- go mod tidy
- git diff --exit-code go.mod go.sum
lint:
stage: test
stage: lint
script:
# Write the code coverage report to gl-code-quality-report.json
# and print linting issues to stdout in the format: path/to/file:line description
Loading
Loading
@@ -252,7 +261,7 @@ lint:
- gl-code-quality-report.json
nilaway:
stage: test
stage: lint
before_script:
- go install go.uber.org/nilaway/cmd/nilaway@latest
script:
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment