Got warning message in CI pipeline
See original GitHub issueHi,
I see this warning in my pipeline and I don’t really know where it comes from: https://github.com/finos/legend-shared/runs/2104257137?check_suite_focus=true
An error occurred while creating the check run for container scan. Error: Error: An error occurred while creating scan result. Statuscode: 403, StatusMessage: Forbidden, head_sha: efc00c4ff11ee8caacfa882e743f8eefb4261af7
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Warning messages for pipeline configurations (!38734) - GitLab
Adds a warning message to the CI lint view; Adds a warning message to the pipeline view; Adds a warning message to the...
Read more >How to display error message on gitlab merge request page ...
I want to display an error message if CI failed to validate the commit messages of the merge request saying Error: some commits...
Read more >CI CD pipeline fails with the following error - Microsoft Q&A
This is Azure Devops reporting an issue when we are trying to run a pipeline. We have changed a parameter in the ARM...
Read more >Pipeline: Basic Steps - Jenkins
Pipeline : Basic Steps · catchError : Catch error and set build result to failure · deleteDir : Recursively delete the current directory...
Read more >Top 10 Most Common Errors In GitLab CI Pipelines - Medium
This is a very generic error. You need to look at the console logs from the beginning to the end to understand which...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@akphi Just want to clarify that this error that you’re seeing in the logs is not because you’ve not installed
Scanitizer
. We just print this message (not a warning or error) in the logs in case the app is not present, and create a check run locally from the action. The users are free to use the action without getting any warnings/errors even if they don’t installScanitizer
.You’re seeing this error because when the action creates a check run locally (for a better summary view), it’s not able to do so because your token doesn’t have enough permissions (because of the limitation that @ds-ms pointed about forked repos).
We were banking on the GitHub Action’s token for creating a check run if the app wasn’t installed. Based on the permissions listed here: https://docs.github.com/en/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token it should have been able to do it, unless if yours is a forked repo. @shigupt202 perhaps we should make this error a little more verbose to point out that it was the ${{ github.token }} which lacked permissions to create a check-run