You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be possible to clone scan a codebase using CxFflow CLI with --github, --gitlab, etc., (that fetches code directly from the repository into CxSAST using a project's source code Location) using a specific commit hash id or commit tag/reference to fetch a specific codebase to scan.
Proposed solution
Add parameters like --commit-hash-id=<COMMIT_HASH> or --commit-ref=<COMMIT_TAG_OR_REFERENCE> when clone scanning with CxFlow CLI using the --github or any other clone scan tag available (like --gitlab) to fetch a specific codebase to scan.
Adding those parameters should also enforce setting the commit hash and/or tag on the ScanRequest object to be able to use them on groovy scripts to allow using those commit hashes and tags to explicitly add scan comments or changing project names.
Another parameter suggestion to avoid using Groovy scripts and simplifying the process to add commit related scan comments would be to add a --commit-info-on-scan-comment=<all|ref|commit-hash> that would add the commit reference (full branch path like "refs/heads/master" or tag), the commit hash or both to the scan comment in the form of -<COMMIT_HASH>" or just "Ref: <COMMIT_TAG_OR_REFERENCE>" or "Commit ID: <COMMIT_HASH>", or probably something simpler like --commit-hash-on-scan-comment=<true|false> and --commit-ref-on-scan-comment=<true|false> that would add information of the commits on a different line of the scan comment, similar to this:
Additional details
The context is allowing ad-hoc scanning, SCMs and other automation servers like Jenkins, Bamboo, TeamCity, etc, to scan specific codebases using a commit hash or tag.
Having #732 and #733 implemented first or at the same time as this feature would be great to be able to clone scan all CxFlow supported SCMs.
The text was updated successfully, but these errors were encountered:
Describe the problem
It should be possible to clone scan a codebase using CxFflow CLI with
--github
,--gitlab
, etc., (that fetches code directly from the repository into CxSAST using a project's source code Location) using a specific commit hash id or commit tag/reference to fetch a specific codebase to scan.Proposed solution
Add parameters like
--commit-hash-id=<COMMIT_HASH>
or--commit-ref=<COMMIT_TAG_OR_REFERENCE>
when clone scanning with CxFlow CLI using the--github
or any other clone scan tag available (like--gitlab
) to fetch a specific codebase to scan.Adding those parameters should also enforce setting the commit hash and/or tag on the ScanRequest object to be able to use them on groovy scripts to allow using those commit hashes and tags to explicitly add scan comments or changing project names.
Another parameter suggestion to avoid using Groovy scripts and simplifying the process to add commit related scan comments would be to add a
--commit-info-on-scan-comment=<all|ref|commit-hash>
that would add the commit reference (full branch path like"refs/heads/master" or tag), the commit hash or both to the scan comment in the form of
-<COMMIT_HASH>" or just "Ref: <COMMIT_TAG_OR_REFERENCE>" or "Commit ID: <COMMIT_HASH>", or probably something simpler like--commit-hash-on-scan-comment=<true|false>
and--commit-ref-on-scan-comment=<true|false>
that would add information of the commits on a different line of the scan comment, similar to this:Additional details
The context is allowing ad-hoc scanning, SCMs and other automation servers like Jenkins, Bamboo, TeamCity, etc, to scan specific codebases using a commit hash or tag.
Having #732 and #733 implemented first or at the same time as this feature would be great to be able to clone scan all CxFlow supported SCMs.
The text was updated successfully, but these errors were encountered: