Skip to content

Warnings written in STDERR fails the build #37

@srikanthraghavan

Description

@srikanthraghavan

Hi Team,
We are using Amazon-Linux as our Github runner where we are trying to integration veracode-sca plugin for agent-based scan. Its interesting that the underlying CURL command fails because of supported OS version.

AS-IS Behaviour:
Run veracode/[email protected]
Start command
curl -sSL https://download.sourceclear.com/ci.sh | sh -s -- scan . --recursive
Error: stderr: WARNING: Veracode SCA agent has not validated support of amzn version 2023

Expected Behavior:

  1. we have an option to pass additional / custom parameters that could be appended to CURL command likes of 2>&1 which redirects STDERR to STDOUT (in case of known scenario)
  2. Handling WARNING as STDOUT and not STDERR that stops the pipeline for the specific warnings
    curl -sSL https://download.sourceclear.com/ci.sh | sh -s -- scan . --recursive 2>&1 | grep -v "Veracode SCA agent has not validated support of amzn version 2023"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions