Closed thaJeztah closed 4 years ago
@ndeloof 🤗
Hm... interesting; https://ci.docker.com/teams-dsg/blue/rest/organizations/jenkins/pipelines/dsg/pipelines/app/branches/PR-624/runs/1/nodes/14/log/?start=0
+ FOSSA_API_KEY=**** BRANCH_NAME=PR-624 make fossa-analyze
docker run -i --rm -e FOSSA_API_KEY \
-e GO111MODULE=on \
-v /home/ubuntu/workspace/dsg_app_PR-624/src/github.com/docker/app/:/go/src/github.com/docker/app \
-w /go/src/github.com/docker/app \
dockereng/fossa-analyzer analyze --option all-tags:true --option allow-unresolved:true --branch PR-624
WARNING Could not determine whether module is built: could not run go list: (exit status 1)
WARNING Module does not appear to be built
FATAL Could not analyze: could not run go list: (exit status 1)
Makefile:115: recipe for target 'fossa-analyze' failed
make: *** [fossa-analyze] Error 1
script returned exit code 2
error is mentioned in https://github.com/fossas/fossa-cli/issues/496 (and a fix in https://github.com/fossas/fossa-cli/pull/439)
/cc @zelahi
Merging #624 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #624 +/- ##
=======================================
Coverage 71.95% 71.95%
=======================================
Files 49 49
Lines 2560 2560
=======================================
Hits 1842 1842
Misses 486 486
Partials 232 232
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 24b127c...59ec475. Read the comment docs.
all green now
Yup, I re-triggered it. Tho I didn't do anything on the fossa side so I'm curious how it happened
Thank you @thaJeztah ❤️
before:
with this PR:
- How to verify it
Ehm, don't know; I don't think the Jenkinsfile change will run on this PR (because I'm not an owner in this repo)
- A picture of a cute animal (not mandatory but encouraged)