This enables the FF_USE_FASTZIP runner feature flag to use the more
performant compression library 'fastzip' within the runner.

This is promising because we spend a significant amount of time waiting
on artifacts and caches to be (de-)compressed (and up-/downloaded). Any
improvement in performance here will compound across all jobs we run.

This prevents the gitlab-crowdin-bot from triggering pipelines in its
MRs if the MR is not yet approved. This should reduce the spam of
skipped (or accidentally not skipped) pipelines from this user, since
they don't provide any value and just clutter the system.

We've seen a 20% improvement in the static analysis jobs with YJIT
enabled.  Let's enable it for all CI jobs.

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

For newer rubies.

Ruby 3.3.6 appears to be ready for testing in GitLab Rails,
Omnibus, and CNG. Bump RUBY_VERSION_NEXT to 3.3.6.

Relates to https://gitlab.com/groups/gitlab-org/-/epics/12350

When BUNDLE_GEMFILE is set to Gemfile.next globally, the QA
jobs should still run it with Gemfile value. Since CI variables
override the local env var values, we need to specify it via a
different env var

Ruby 3.2 has been made the default in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/168129

, but we
missed to update the omnibus-gitlab cache key.

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

Changelog: added

This commit allows running a pipeline with
BUNDLE_GEMFILE: Gemfile.next if pipeline:run-with-rail-next
label is set

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

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.