This should not affect any actual behaviour because it should still read
and write with the described strategy. We just additionally also write
another mapping file for coverage strategy so that we can compare them.

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

Use the repo from artifacts in frontend jobs

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/158197



Merged-by: Lin Jen-Shin <jen-shin@gitlab.com>
Approved-by: Lin Jen-Shin <jen-shin@gitlab.com>
Reviewed-by: Rémy Coutable <remy@rymai.me>
Reviewed-by: Lin Jen-Shin <jen-shin@gitlab.com>
Co-authored-by: Rémy Coutable <remy@rymai.me>

(cherry picked from commit 2f83fd5b)

6b02c833 Use the repo from artifacts in frontend jobs
34c0263b Move frontend test to new test-frontend stage
33e3b22c ci: Don't use repo from artifacts for critical jobs

Co-authored-by: Lin Jen-Shin <jen-shin@gitlab.com>

This reverts merge request !158197

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

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

Move them into a separate so it can be included by templates or
projects.

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

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

Co-authored-by: Ash McKenzie <amckenzie@gitlab.com>

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

This reverts merge request !152687

The ruby 3.1 image doesn't exist yet.

This commit adds `OMNIBUS_RUBY_VERSION` and `CNG_RUBY_VERSION` to
define which versions are used in the Omnibus and CNG projects.

Previously the Ruby versions used in the child pipelines for building
Omnibus and CNG was determined based on the image used in the
respective CI jobs. When we bumped the CI image to 3.1.5 in
https://gitlab.com/gitlab-org/gitlab-build-images/-/merge_requests/803,
this quietly added a requirement to Omnibus that Ruby 3.1.5 had to be
supported. At the same time, the `build-cng` image used Ruby 3.1.4, so
https://gitlab.com/gitlab-org/build/CNG-mirror/-/jobs/6821715942
started to fail once CNG stopped building Ruby 3.1.4.

While the latter case needed
https://gitlab.com/gitlab-org/build/CNG/-/merge_requests/1828, we can
at least avoid the first problem by explicitly setting the version
needed. In an ideal world, these variables would be determined
automatically from the upstream projects. However, setting these
variables avoids surprise failures and opens the possibility up for
automation to update these values.

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

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

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

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

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

This is needed in preparation of updating nodejs from 18.17 to 20.12
since the former is nearing end-of-life. In addition, the updates to
npm and its node-gyp dependencies will fix support for Python 3.12.

Relates to
https://gitlab.com/gitlab-org/gitlab-development-kit/-/issues/2081

adding the "pipeline" suffix isn't needed for pipeline names.

Also, the CI_MERGE_REQUEST_EVENT_TYPE is already shown
in the UI, so it's redundant to have it in the name.

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

We already chose to switch to cssbundling per default about a week ago:
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/144479

We haven't seen any regressions in production (apart from the UTF-8 fix
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/145363 needed). So
it is probably safe to move forward with the removal of the old SCSS
compiler.

After analyzing the CSS diff between the new and old compiler, the diff
doesn't have us concerned too much. We therefore want to enable the new
SASS compiler in CI/CD to see if there are any failures.

Furthermore we turn it on in development by default as well

- See also: https://gitlab.com/gitlab-org/gitlab/-/issues/438278
- Link to the Diff:
  https://gitlab.com/gitlab-org/frontend/playground/sass-compiler-diff/-/merge_requests/1#note_1758213709

This will allow the FIPS jobs to run without having to reinstall
Ruby gems and recompile Gitaly and Workhorse.

Replace `DEBIAN_VERSION` and hard-coded `debian` values in favor
of `BUILD_OS` and `OS_VERSION` variables.

Simplify the `setup-test-env-fips` CI step now that `libpq-devel` is
now in the UBI image
(https://gitlab.com/gitlab-org/gitlab-build-images/-/merge_requests/775).

Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/441519

Cloud Native GitLab already ships with Debian bookworm, so
we should update this too. This is also needed to reduce
the number of build images we produce.

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

CI_PROJECT_PATH should be set as the path where it's running the
pipeline, and in the case of Gitaly triggering a cross project
pipeline, it is `gitlab-org/gitlab` rather than `gitlab-org/gitaly`.

That said, checking the variable doesn't really make sense, because
it's likely the pipeline wouldn't really run if anything else than
`gitlab-org/gitlab` is set. This variable is used in a lot of places,
changing it will likely to break random things, so it should be just
assumed and it should not be changed.

Also CI_PIPELINE_SOURCE should be `pipeline` for cross project
pipelines.

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