Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Commiting coverity scan results on Connect server #252

Open
lzo2 opened this issue Oct 1, 2024 · 0 comments
Open

Commiting coverity scan results on Connect server #252

lzo2 opened this issue Oct 1, 2024 · 0 comments

Comments

@lzo2
Copy link

lzo2 commented Oct 1, 2024

When running this action v1.13.0, I can fully scan my project source code with coverity and the results are generated locally. Everything works fine and now I need to upload the results on the company Connect server.
Is there any option to execute the Coverity Connect Commit step with that github action ? or should I add a new step to manually execute a coverity commit. Any tips for commiting results is welcome.

Thanks and regards
-Lzo

      # SCA - Coverity using synopsys-action@1.13.0
      - name: Coverity Full Scan
        uses: synopsys-sig/synopsys-action@2b8476cc491cd5515ee04e3c215698bfd8523504
        with:
          ### Coverity Connect users
          coverity_local: true

          ### Scanning required fields
          coverity_url: ${{ vars.COVERITY_URL }}
          coverity_user: ${{ vars.COVERITY_USER }}
          coverity_passphrase: ${{ secrets.COVERITY_PASSPHRASE }}
          coverity_project_name: ${{ github.event.repository.name }}
          coverity_stream_name: ${{ github.event.repository.name }}-master
          coverity_policy_view: 'Outstanding Issues'

          ### Arbitrary product-related CL arguments
          coverity_build_command: cmake --build ./build --target all
          coverity_clean_command: cmake --build ./build --target clean
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant