Skip to content

Don't use Markdown cache for stubbed settings in specs

Sean McGivern requested to merge ignore-markdown-cache-when-stubbing-application-settings into master

What does this MR do?

When we use stub_application_setting, disable the Markdown cache on ApplicationSetting. Because we're stubbing, not doing an actual DB update, any cached Markdown from previous spec runs would not be updated.

Are there points in the code the reviewer needs to double check?

¯\＿(ツ)＿/¯

Why was this MR needed?

We have a spec failure in master.

What are the relevant issue numbers?

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/41130.

Merge request reports