Using a relative namespace incorrectly fetches `Ci::Sources::Project`
in EE

Project-level secure files are now sorted by the time they are created.

Changelog: changed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/87546

This commit refactors how we fetch the next batch
of artifacts that needs to be updated. It creates new
scopes for Ci::JobArtifacts and order the result data
by ascending (created_at, id).

To track if ever we miss any entrypoints that may cause
artifact deletion while project is undergoing refresh, we
added some log calls.

This commit removes a worker used to remove artifacts for
a given job. Prefer using ExpireBuildArtifactsWorker which
is more performant.

Niklas authored 2 years ago and Ethan Urie committed 2 years ago

Changelog: added
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/361643

This sets the data_consistency for the Ci::ArchiveTraceWorker to
sticky. Allowing the read queries before any write to be handled by a
replica.

The job is scheduled from the Ci::BuildFinishedWorker with some delay
built in. Which means this job can take the 0.8s wait in the
beginning, and is very likely to find a replica that is up to date
with the WAL locations at the time of scheduling.

To increase the effect of this, this also preloads some associations
in the worker. That way, we can take advantage of loading them from a
replica rather than doing it lazily from the primary.

This commit cleans up ci_reduce_persistent_ref_writes
feature flag.

Changelog: other

This applies to the following situations:
- REST API calls
- GraphQL API calls when "legacyMode" is unset or
  set to default value of "14.5".

See https://gitlab.com/gitlab-org/gitlab/-/issues/347303

Changelog: changed

Pedro Pombeiro authored 2 years ago and Doug Stull committed 2 years ago

Changelog: removed

Albert Salim authored 2 years ago and Fabio Pitino committed 2 years ago

This opens the runner job artifact request API to requests that
use either of the following tokens:
1. Job token belonging to the job that owns the artifact (existing behaviour).
   This token is valid regardless of the status of the job.
2. Job token belonging to the job that depends on the artifact (new behaviour).
   This token is valid only if the dependent job is still running.

The permissions attribute in the Secure Files model is not used and has been removed.

Changelog: changed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/86598

Changelog: added

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

This removes all `default_enabled: :yaml | true | false`

This has been a deprecated no-op since 14.0. It was never documented and
no GitLab-provided CI/CD template has relied on it since 14.0.

See https://gitlab.com/gitlab-org/gitlab/-/issues/333441

Changelog: removed

Furkan Ayhan authored 2 years ago and Sean Arnold committed 2 years ago

We want to show included files on the CI Linter page.
To do that, backend needs to send this information to frontend
via the ciConfig result.

Changelog: other

Pedro Pombeiro authored 2 years ago and Terri Chu committed 2 years ago

Changelog: deprecated

Pedro Pombeiro authored 2 years ago and GitLab Release Tools Bot committed 2 years ago

Merge branch 'pedropombeiro/330047/use-protected-suffix-for-cache-name' into 'master'

See merge request gitlab-org/security/gitlab!1551

Changelog: security

Changelog: fixed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/85963
EE: true

Laura Montemayor authored 2 years ago and Fabio Pitino committed 2 years ago

Changelog: changed

This MR removes our coverage detection at the projet setting level.
It is still possible to parse coverage from job log by using the
coverage keyword.

Changelog: deprecated

Mehul Sharma authored 2 years ago and Simon Tomlinson committed 2 years ago

Dropped runner_features column from ci_build_metadata

Changelog: changed

This change removes the ability to convert a instance (shared) runner
to a project (specific) runner.

Changelog: removed

This commit reduces the persistent ref creation
for pipelines.

Fabio Pitino authored 2 years ago and Marius Bobin committed 2 years ago

Logged details can help making informed decisions on
limit thresholds for pipeline hierarchy sizes.

Niklas authored 2 years ago and Fabio Pitino committed 2 years ago

Changelog: fixed
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/356758

Fix issues with extra non-applicable statuses in
the STARTED_STATUSES array

This commit fixes the regression that unrelated environments
are teardown when a MR has been merged/closed.

This fix is still behind the feature flag.

We support variables for YAML attributes of environment:name and
environment:url. However, we expand those variables only 1-level.
In this commit, we start supporting infinite level expansion.

These changes are behind a FF ci_expand_environment_name_and_url

Furkan Ayhan authored 2 years ago and Jan Provaznik committed 2 years ago

Pipeline schedule variables have the same priority
as pipeline variables.
We decided that we could consider pipeline schedule variables
as pipeline variables.