Skip to content

Additional build/pipeline tool discovery from fcli action run ci #732

@kadraman

Description

@kadraman

Enhancement Request

It would make sense to add the "auto-discovery" of more build/pipeline tools other than current GitHub/GitLab/Azure DevOps. Probably next most common is Jenkins, which could be something like:

  # Jenkins
  - if: ${#isNotBlank(#env('JENKINS_HOME'))}
    var.set:
      global.ci.name:              Jenkins
      global.ci.id:                jenkins
      global.ci.qualifiedRepoName: ${#env('GIT_URL').replaceAll('[^:]+://[^/]+/','').replaceAll('\.git$', '')}
      global.ci.sourceBranch:      ${#env('JOB_BASE_NAME'):#env('GIT_NAME')}
      global.ci.commitSHA:         ${#env('GIT_COMMIT')}

This assumes GIT is being used. Other popular build/pipelines tools I'm aware of Fortify customers using are: TeamCity, BitBucket and CircleCI.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions