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>

This reverts merge request !154814

This is based on:

* Use `allow_failure: true` on the job so that we don't mess with rules
* Use the same rules for both because manual actions are done by the
  other means, and we no longer need to mix the rules with manual vs
  automated one.

This also drops rules around if-force-ci because it should not be used

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

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

This reverts merge request !152687

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>

This should make the intention more clear and avoid messing up

This will make it easier to read the output of that job
when debugging predictive backend pipelines.

As described in https://wiki.alpinelinux.org/wiki/Edge, `alpine:edge`
is a development branch and should not be used in production. Prefer
`alpine:latest` since this uses the latest stable version.

Currently `alpine:edge` is broken with curl:

```
$ docker run -it alpine:edge  sh
/ # apk add --no-cache --update curl bash jq
fetch https://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
(1/16) Installing ncurses-terminfo-base (6.4_p20240309-r0)
(2/16) Installing libncursesw (6.4_p20240309-r0)
(3/16) Installing readline (8.2.10-r0)
(4/16) Installing bash (5.2.26-r0)
Executing bash-5.2.26-r0.post-install
(5/16) Installing ca-certificates (20240226-r0)
(6/16) Installing brotli-libs (1.1.0-r1)
(7/16) Installing c-ares (1.27.0-r0)
(8/16) Installing libunistring (1.2-r0)
(9/16) Installing libidn2 (2.3.7-r0)
(10/16) Installing nghttp2-libs (1.60.0-r0)
(11/16) Installing libpsl (0.21.5-r1)
(12/16) Installing zstd-libs (1.5.6-r0)
(13/16) Installing libcurl (8.6.0-r1)
(14/16) Installing curl (8.6.0-r1)
(15/16) Installing oniguruma (6.9.9-r0)
(16/16) Installing jq (1.7.1-r0)
Executing busybox-1.36.1-r21.trigger
Executing ca-certificates-20240226-r0.trigger
OK: 16 MiB in 30 packages
/ # curl
Error relocating /usr/lib/libcurl.so.4: SSL_get0_group_name: symbol not found
```

Relates to:

* https://github.com/alpinelinux/docker-alpine/issues/383
* https://gitlab.com/gitlab-org/release/tasks/-/issues/9635

This way we avoid mixing different builds, that is mixing ruby versions

The detect-tests job is failing in
https://gitlab.com/gitlab-renovate-forks/gitlab/-/jobs/6326977771
because `ruby:3.1-slim` doesn't come with `gcc` and `make`, which is
needed to build native extensions. `activesupport` depends on `i18n`,
which depends on `racc`. `racc` has a native extension.

Create script for check default pipeline status

source util.sh

The default is 3.1.4 if NEXT_RUBY_VERSION is not presented

* Default: 3.1
* Merge requests: Default (3.1)
* Default branch: Default (3.1)
* ruby3_0 branch: Old (3.0)
* ruby3_2 branch: Next (3.2)
* With labels: Use the respective versions

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

This reverts commit 11a9729c

Refactor

Add testing commit, will be removed

Removes testing commit

Lin Jen-Shin 创作于 1 year ago ，Jennifer Li 提交于 1 year ago

When label ~"pipeline:run-in-ruby3_0" is provided, run in Ruby 3.0
instead.

Sanad Liaquat 创作于 1 year ago ，Lin Jen-Shin 提交于 1 year ago

Post the message only when the trigger-omnibus-and-follow-up-e2e
is available

Sanad Liaquat 创作于 1 year ago ，Lin Jen-Shin 提交于 1 year ago

Also make trigger-omnibus-env job automatic

Set correct ee variable value for omnibus ce trigger

Add missing dependency on omnibus-trigger for old-nav pipeline

Message will be posted if QA_TESTS have folders only

Since we're going to postgres 14 on gitlab.com, we should make that
the primary version we test against, and we should add nightly tests
for postgres 15

Changelog: changed