Skip to content

tests: Move rake assets:precompile and cloning gitlab-{shell,test} to the prepare stage

What does this MR do?

Move some processing previously done in every job in the test stage to the prepare stage. Specifically: rake assets:precompile and TestEnv.init (which includes git clone https://gitlab.com/gitlab-org/gitlab-{shell,test})

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

Why was this MR needed?

Running our test suite is computationally intensive and quite sensitive to network / GitLab.com problems. This change improves that situation a bit.

Screenshots (if relevant)

Screen_Shot_2016-11-16_at_20.59.37

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

Related to #23034 (closed)

Merge request reports