Closed Jalle19 closed 3 months ago
@catalinii can you double-check that there's a secret named COVERITY_SCAN_TOKEN
?
Yes COVERITY_SCAN_TOKEN exists
@catalinii is it the same value as in your minisatip-build-image repository? I can't find a reason why the downloading of the client doesn't work
@catalinii can you send me the token via e-mail or WhatsApp or soemthing so I can try this locally?
Okay so the command works fine, but the token is not being read by GitHub for some reason
not sure but could this help
curl \
--form token=$TOKEN \
It simply doesn't work. @catalinii are you really sure the secret is defined in this project?
It could be that it won't work for pull requests, otherwise anyone could make a PR that logs the token. We should try changing the action to only run against the master branch (makes more sense anyway) and merge this, then deal with the eventual fallout.
Coverity Build Capture (64-bit) version 2023.12.2 on Linux 6.5.0-1025-azure x86_64
Internal version numbers: 78329b8295 p-2023.12-push-50
make: *** No targets specified and no makefile found. Stop.
Warning: Build command make exited with code 2. Please verify that the build completed successfully.
Warning: No files were emitted. This may be due to a problem with your configuration
or because no files were actually compiled by your build command.
Please make sure you have configured the compilers actually used in the compilation.
For more details, please look at:
/home/runner/work/minisatip/minisatip/cov-int/build-log.txt
Error: Process completed with exit code 2.
Let's see if this works