JakeHillion/storj
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Jenkinsfile: clarify modfile linting

Browse Source 
Change-Id: I0ac0bfa48386d3430eb8fb5a92b57daefc23998f
This commit is contained in:
Egon Elbre 2021-08-31 15:13:45 +03:00
parent 3510bc036e
commit 25971c581f
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Jenkinsfile.public
View File

@ -20,7 +20,8 @@ pipeline {
steps { steps {
checkout scm checkout scm
sh 'mkdir -p .build' sh 'mkdir -p .build'
// make a backup of the mod file in case, for later linting // make a backup of the mod file, because sometimes they get modified by tools
// this allows to lint the unmodified files
sh 'cp go.mod .build/go.mod.orig' sh 'cp go.mod .build/go.mod.orig'
sh 'cp testsuite/go.mod .build/testsuite.go.mod.orig' sh 'cp testsuite/go.mod .build/testsuite.go.mod.orig'
@ -128,7 +129,6 @@ pipeline {
sh 'check-errs ./...' sh 'check-errs ./...'
sh 'staticcheck ./...' sh 'staticcheck ./...'
sh 'golangci-lint --config /go/ci/.golangci.yml -j=2 run' sh 'golangci-lint --config /go/ci/.golangci.yml -j=2 run'
// Why don't we run mod tidy on the actual mod instead.
sh 'check-mod-tidy -mod ../.build/testsuite.go.mod.orig' sh 'check-mod-tidy -mod ../.build/testsuite.go.mod.orig'
} }
} }