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.

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>

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

Stan Hu 创作于 1 year ago ，Lin Jen-Shin 提交于 1 year ago

Now that Ruby 3.1.4 is in production, move to Ruby 3.2.2 to take
advantage of YJIT.

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

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

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

We regularly see community contributors running out of pipeline minutes
because they forgot to use `-o ci.skip` while pushing the updated
master branch to their fork.

Currently we advise them to switch to the community fork to prevent them
to use up their quota again, but that doesn't help them in the current
month when they also use CI for other projects in their namespace.

We can disable these pipelines entirely as they serve no purpose on forks.
This should help community contributors to not accidentially use up their
entire pipeline minutes quota for the rest of the month.

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.

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>

- Enables auto_explain for postgres >=14 in CI
- Merges and deduplicates these logs to generate an example plan for
  each query, if the pipeline:record-queries label is present

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

The project path in the workflow rules for a gitaly test pipeline is
incorrect. Fix it.

The job is called “benchmark-markdown” and is in
the “post-test” stage.

Move the GITALY_TEST rule up to the top before the FORCE_GITLAB_CI rule
since we will be setting the FORCED_GITLAB_CI.

Failed specs can take a long time to run, due to potential timeouts
before reaching those errors. This currently makes some RSpec jobs
run for a long time, and this lengthen the pipelines duration.

This commit introduces a limit to the number of failures before
we fail the RSpec job that ran them (defaults to 20 for now)

It's done to make it compatible with 1.20 Golang

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

Link to the issue so we know when it's resolved.
Still keep it there because when it works it'll work,
and we don't need to update it. We should remove the
comment then but it can get to work first.