Skip to content

AutoDevOps stills triggers the License Scanning Job even after License Scanning was deprecated

Summary

GitLab's AutoDevOps still triggers the standalone license scanning job even though this functionality has been deprecated and moved under the dependency scanning functionality. The job will run yet fail with a warning. The job log suggests to disable the license scanning job:

image

Disabling the job is not possible when the project is set to use AutoDevOps through the project settings (i.e. no .gitlab-ci.yml file is present). Though the pipeline does not stop on this job failure the message is confusing to anybody investigating the job log.

Steps to reproduce

Run AutoDevOps on any project that has languages supported by our scanners:

image

Example Project

What is the current bug behavior?

The standalone License Scanning job still runs as part of AutoDevOps even though this has been deprecated. The job fails with warning (allowed to fail)

image

The job log contains confusing suggestions on how to fix the situation when no .gitlab-ci.yml is present

What is the expected correct behavior?

Separate license scanning job should not get triggered as part of AutoDevOps. The simplest approach might be to set LICENSE_MANAGEMENT_DISABLED to true in the AutoDevOps template, so that users do not worry about the license scanning job (autodevops includes dependency scanning which is what handles this now)

Relevant logs and/or screenshots

See above

Output of checks

This bug happens on GitLab.com

/label reproduced on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

Set LICENSE_SCANNING_DISABLED to "true" in the Auto DevOps template.

Edited by Fabien Catteau