Skip to content

Resolve "Isolate elasticsearch-using specs"

Nick Thomas requested to merge (removed):4986-isolate-elasticsearch-specs into master

What does this MR do?

Stores the CE set of services for specs common to CE and EE, restricting elasticsearch to EE-only jobs.

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

Why was this MR needed?

The EE service takes up a lot of RAM, and is unnecessary for CE-only specs. Since the test suite reorganization, it's now possible to restrict the service only to EE jobs and reduce the CE->EE diff in .gitlab-ci.yml marginally too.

Hopefully this speeds up the EE spec run a bit and makes it more reliable.

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

  • Tests added for this feature/bug
  • Has been reviewed by Backend
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Squashed related commits together
  • Internationalization required/considered
  • If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan
  • End-to-end tests pass (package-qa manual pipeline job)

What are the relevant issue numbers?

Closes #4986 (closed)

Merge request reports