License Scanning job does not "configure" License Compliance
Summary
Currently the License-Management.gitlab-ci.yml template is what marks License Compliance as Configured on the Security & Compliance > Configuration page. The License-Scanning.gitlab-ci.yml template does nothing to mark that as configured.
Steps to reproduce
(How one can reproduce the issue - this is very important)
If you create a new project, and add the License Scanning template, you'll get the following result:
You can see that it is not marked as configured:
Even though the License Scanning job has been run:
This is on GitLab 12.9.0 (on GitLab.com).
Example Project
Here's an example project: https://gitlab.com/poffey21/license-compliance/
What is the current bug behavior?
(What actually happens)
The Configure page does not recognize the License Scanning results as valid results for marking License Compliance as Configured.
What is the expected correct behavior?
(What you should see instead)
The License Scanning job ought to mark License Compliance as Configured.
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens 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
(If you can, link to the line of code that might be responsible for the problem)
Not a possible fix, but I assume this file is the right place to get started: