GitLab

In https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27001 we
introduced a step that will clean up file based variables. However if we
are still running this stage even if there is no file based variables
defined. If we keep running the step no matter what we are wasting
compute resources and it wouldn't be consistent with our other steps
where they are skipped it it would be a no-op.

Update the test to create a brand new `build` and `info` so the
JobVariables aren't "cached" from the previous run.

closes https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27057

Improve build logging testing

See merge request gitlab-org/gitlab-runner!2465

Clarify how service_account in toml is used

See merge request gitlab-org/gitlab-runner!2476

Provide a full list of metrics available for GitLab runners in the documentation

See merge request gitlab-org/gitlab-runner!2479

Fix TestBuildCancel from timing out

Closes #27077

See merge request gitlab-org/gitlab-runner!2468

In https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27077 we are
seeing timeouts of the `TestBuildCancel` test because when the job in
canceled we send `SIGTERM` to process that is running. After a certain
amount of time we send `SIGKILL` if that process hasn't terminated yet,
the default is [10
minutes](https://gitlab.com/gitlab-org/gitlab-runner/-/blob/56fbbb1150681915e4de33551a01cb3d4defa91c/helpers/process/killer.go#L17).
Since the default timeout of go tests is 10 minutes our test ends up
timeing out because `SIGKILL` hasn't been sent yet.

Have the GracefulKillTimeout and ForceKillTimeout configurable and set
it at a low amount for tests so we don't waste time waiting for a
process to terminate since the processes don't usually have any cleanup
to do.

closes https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27077

Introduce usage of Runner Manager terminology

See merge request gitlab-org/gitlab-runner!2474

Related to https://gitlab.com/gitlab-org/gitlab/-/issues/250481

Teach artifact/cache commands about the archive interface

See merge request gitlab-org/gitlab-runner!2467

Update Kubernetes' documentation to include ephemeral storage requests/limits

Closes #27059

See merge request gitlab-org/gitlab-runner!2457

Implement archiver/extractor interface

See merge request gitlab-org/gitlab-runner!2195

This job is causing a few problems:
1. Preventing forks from running https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27021
1. Blocking releases because pipelines on tags fail https://gitlab.com/gitlab-org/gitlab/-/issues/263711

Revert "Merge branch 'ajwalker/after_script-kamil' into 'master'"

See merge request gitlab-org/gitlab-runner!2469

This reverts commit 411b98f3, reversing
changes made to 689cf710.

Allow runner to archive cache on failure

See merge request gitlab-org/gitlab-runner!2416

Stylistic changes based on review

`cache:when` is used to cache on job failure, despite the failure.

`cache:when` can be set to one of the following values:

1. `on_success` - upload artifacts only when the job succeeds.
   This is the default.
2. `on_failure` - upload artifacts only when the job fails.
3. `always` - upload artifacts regardless of the job status.

Doc `cleanup_file_variables` for custom executor

See merge request gitlab-org/gitlab-runner!2455

Report Kubernetes pods' conditions when they're pending

Closes #4569

See merge request gitlab-org/gitlab-runner!2434

Merge branch '27068-metrics-specify-that-a-job-has-failed-succeeded-even-when-running-after_script-which-breaks' into 'master'

Detach runtime state/metric from CI_JOB_STATUS

Closes #27068

See merge request gitlab-org/gitlab-runner!2462

Ensure that for abort only abort is called

Closes #27056

See merge request gitlab-org/gitlab-runner!2463

Previously we would call `cancel()` on `abort()`
which in some implementations could result
in calling additional steps due to race condition.

The `abort()` is final, we don't need to `cancel()` before
as `abort()` in any case should take a precedence
in processing.