Add support for license scanning jobs that have been extended in .gitlab-ci.yml
It seems that License Compliance does not support jobs that generate artifacts from jobs that extend
from the license-scanning
job. This bug, or needed feature improvement was discovered by dogfooding our demo project.
Problem:
Using the extend
keyword in .gitlac-ci.yml and creating jobs that extend from license-scanning
yields json artifacts that are not license-scanning.json
which license compliance expects.
Instead we get things like license-scanning-go.json
and license-scanning-c.json
when a user defined different artifact names as part of a job that extends
from license-scanning
See:
https://gitlab.com/gitlab-examples/security/security-reports/-/blob/master/.gitlab-ci.yml#L29
Endpoint:
Jobs:
https://gitlab.com/gitlab-examples/security/security-reports/-/pipelines/176676330
license-scanning-go
https://gitlab.com/gitlab-examples/security/security-reports/-/jobs/681001814
license-scanning-c
https://gitlab.com/gitlab-examples/security/security-reports/-/jobs/681001816
What we see in the UI:
https://gitlab.com/gitlab-examples/security/security-reports/-/licenses#licenses