Workaround 3: Upgrade to GitLab 13.x and use the defaults. Workaround 2: Disable Docker-in-Docker for SAST and Dependency Scanning (GitLab 12.3 and later). Workaround 1: Pin analyzer versions (GitLab 12.1 and earlier). SAST job fails with message strconv.ParseUint: parsing "0.0": invalid syntax. Semgrep slowness, unexpected results, or other errors. SpotBugs Error: Project couldn't be built. SpotBugs UTF-8 unmappable character errors. Error: sast is used for configuration only, and its script should not be executed. Getting warning message gl-sast-report.json: no matching files. Error response from daemon: error processing tar file: docker-tar: relocation error. exec /bin/sh: exec format error message in job log. Pipeline errors related to changes in the GitLab-managed CI/CD template. Configure certificate checking of packages. Set SAST CI/CD variables to use local SAST analyzers. If support for Custom Certificate Authorities are needed. 
Make GitLab SAST analyzer images available inside your Docker registry. Using a CI/CD variable to pass username and password to a private Maven repository. Using a CI/CD variable to pass username and password to a private Go repository. 
Using CI/CD variables to pass credentials for private repositories. Configure SAST in the UI with default settings only. Configure SAST in the UI with customizations. 
Enable multi-project support for Security Code Scan.
0 kommentar(er)
