License Scanning temporarily disabled

No licenses will be detected unless the license scanning template is explicitly included in your .gitlab-ci.yml file. Our engineering team is working to restore full functionality. Details in this issue: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/8593

We are evaluating several potential resolutions. Next update in one hour. To ensure your license scan runs correctly, explicitly include the template per the documentation here:
https://docs.gitlab.com/ee/user/compliance/license_compliance/#include-the-license-scanning-template

A resolution approach has been decided upon, but it will take time to implement. You can include the license scanning template to ensure proper detection while our engineering team continues working. Expect the next update in 24 hours unless there's new information before.

Our engineering team continues to work to restore full license scanning operation. Explicitly including the license scanning template in your CI configuration will allow scans to run correctly. Next update will be Monday, March 27th unless there is news to share sooner.

Our engineering team has a merge request to fix this issue; it is being reviewed and can be followed at https://gitlab.com/gitlab-org/gitlab/-/merge_requests/115773. At this time we anticipate the fix should be merged within one to two days. Explicitly including the license scanning template in your CI configuration will allow scans to run correctly. The cu

We have deployed a merge request to address the issue. We are currently reviewing this and will continue to monitor the situation. You can refer to the incident issue https://gitlab.com/gitlab-com/gl-infra/production/-/issues/8593 for more details.

License scanning has now been re-enabled. The optimizations in place have proven to reduce significantly the performance issues on the database. We will continue to monitor.
Further details can be found here: https://gitlab.com/gitlab-org/gitlab/-/issues/398679