Add needs for all jobs which require setup-test-env and
move review-build-cng to additional stage review-prepare
to decrease wait time for jobs in pipeline

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Part of: https://gitlab.com/gitlab-org/gitaly/issues/1715

* 9.6.11 -> 9.6.14
* 10.7 -> 10.9

This is done in preparation for upgrading PostgreSQL in Omnibus:
https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/3492

Changes * to + to be more precise with acceptable branch names

With https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/30254 Junit
reports were disabled. With
https://gitlab.com/gitlab-com/gl-infra/production/issues/928 and
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/30274 solved we
should enable them again.

closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64756

Log memory stats after running each spec file and compile the report.

This reverts merge request !30130

Specify the minor version of postgresql for CI

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

The junit reports are creating 90mb files inside of redis for
`gitlab-ce/ee` project. There is an ongoing production incident
https://gitlab.com/gitlab-com/gl-infra/production/issues/928 that is
because of high CPU uitlaization on the redis nodes. GitLab-ce/ee are
the highest consumers of memory becuase of these junit reports.

This is a bandage until we can scale redis properly.

We repeat the same code in many places. With the support of multiple
extends, we can clean up several jobs.

If you chose to use the rollback migration feature on your current
version for example, you should still have a way to migrate, being
that you are still on a supported migration path.

MySQL support has been removed

One can not upgrade straigt from 9.3 to 12.0, due to the schema changes
being backported. Instead, one must first upgrade to 11.11.X. Omnibus
already enforces this, and our online upgrade guidelines also cover
this.

By changing the CI config we don't have to adjust the backport migration
to handle a migration path that one can not take.

Also update dependencies to match updated job names

This updates our build images to use node@12. We are also adding a
sentence to the from-source installation that while we require a minimum
version of node@8, we also recommend node@12. Last but not least, we
change the version of node in the .nvmrc so that developers using nvm
can automatically use node@12 with the project

This commit adds CI job that validates all `*.yml`
with `yamllint`.

This commit fixes all offenses present in repository.

[run mysql]

Signed-off-by: Rémy Coutable <remy@rymai.me>

This reverts commit 744f1f2e, reversing
changes made to c4d930e5.

This reverts merge request !27514

Signed-off-by: Rémy Coutable <remy@rymai.me>

Ruby 2.6 offers better performance and memory usage:
https://www.rubyguides.com/2018/11/ruby-2-6-new-features/

Part of https://gitlab.com/gitlab-org/gitlab-ce/issues/57323

Signed-off-by: Balasankar "Balu" C <balasankar@gitlab.com>

Attempt to solve issues such as
https://gitlab.com/gitlab-org/gitlab-ce/issues/60953.

Given Rails doesn't use the Git binary anymore, this shouldn't be a
problem.