QA test for code_quality for AutoDevOps
In gitlab-qa#323 (closed) we decided to disable it[0] because it's timing out very often and broke the tests.
We should enable it or add another test for it.
Quoting @DylanGriffith here:
The team who owns
code_quality
could prioritise speeding this up since this test project is just a few lines of ruby code it really should not take so longUpdate the test so that we disable the code quality by setting an env var through the UI. The downside is that
code_quality
won't be executed in CI anymoreWe increase the timeout even further. But I'm not sure what is the limit of how long
code_quality
may take in the worst case and since it's somewhat of a blackbox to me I have no idea why it's taking so long in the first place.
[0]: To be clear, we already disabled it but it didn't properly disable it, and https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/21709 fixed that.