Skip to content

Unexpected fortify directory included on Gitlab payloads without build integration #947

@gilseara

Description

@gilseara

Current Behavior

When using -bt none on Gitlab integrations a "fortify" directory is being included in the package due to Gitlab structure

Expected Behavior

Directories that are not part of the repository should not be included on the package

Steps To Reproduce

  1. Run a pipeline on Gitlab
  2. Check the resulting artifact
  3. Verify that a "fortify" directory with logs and data is included on the package)

Environment

Pipeline include: 
 
component: $CI_SERVER_FQDN/Fortify/components/ast-scan/linux@1.0.1
      inputs:
        job-name: fortify-sast
        stage: test
        fcli-version: v3

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions