Configure environment variables for CVE scanning#1717
Conversation
Added environment variables for OSS_INDEX_USERNAME and OSS_INDEX_PASSWORD in CVE scanning workflow.
✅ Deploy Preview for fdc3 canceled.
|
kriswest
left a comment
There was a problem hiding this comment.
LGTM - the check is still failing but may only pass once this is merged??
|
Hi @kriswest yes. The problem is that forks cannot access secrets. |
So it had to be merged before it would work in the scheduled scans - next one happens overnight. Will it be able to scan PRs (so we can use it as a check)? |
|
No dice, this scheduled scan on main still failed after this merged: https://github.com/finos/FDC3/actions/runs/20106913440/job/57693352931 |
|
If memory serves it requires a bot of some sort (we need to switch to codecov for the same reason, the forks can't post coverage comments... It looks like this has been a limitation since 2021 and has never been prioritised: https://community.sonarsource.com/t/code-analysis-on-pull-request-from-forked-repository-with-github-actions/43986 Perhaps that makes this the wrong tool for the job in an OS foundation. We expect to take contributions from new contributors/non-maintainers regularly...
Does FINOS have a view or future plans on this front? |
|
@kriswest agree that this is not ideal as the typical workflow is to raise PRs via forks. The TOC is aware and areworking on updating the (outdated) dependency management section of the FINOS community website with new recommended tools. They are looking at it right now so we should have some updated very soon. |
|
@TheJuanAndOnly99 great to hear the TOC is looking at it - let us know if they update the advice (including if we should switch to whitesource - I believe we're using finos code scanning currently) |
Added environment variables for OSS_INDEX_USERNAME and OSS_INDEX_TOKEN in CVE scanning workflow. The secrets have also been added to the repo.