Pipeline Security tab returns 500
Summary
The pipeline security tab is not reporting vulnerabilities anymore because of a 500 error.
Steps to reproduce
or any other pipeline apparently on gitlab.com.
Example Project
Any project on gitlab.com with security jobs enabled.
What is the current bug behavior?
500 instantly returned by the backend (it's not a timeout).
What is the expected correct behavior?
Vulnerabilities detected in the pipeline
Relevant logs and/or screenshots
Output of checks
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)