Since it is not possible to dynamically detect if a job is automatically
cancellable or not, a this new attribute is necessary. Moreover, it let
the maintainer of the repo to adjust the behaviour of the auto cancellation
feature to match exactly what he needs.

This is to accomodate prepended modules.

This commits avoiding conflicts between ArchiveTraceWorker
and ArchiveTracesCronWorker by changing the target of the
latter worker.

This toggles the ci_dag_support flag to be on by default.
This relies on ci_dag_limit_needs to be present to reduce
amount of inter-dependencies between jobs

This makes us to expand variables only when needed,
instead of requesting all variables each time.

This specifically helps in situation when explicit name
of `environment: production` is used.

When `needs:` is defined, the value of it is
not respected when returning a list of artifacts
to the runner from the job.

This implements the support for `needs:` keyword
as part of GitLab CI. That makes some of the jobs
to be run out of order.

Adds Job specific variables to facilitate specifying variables when
running manual jobs.

Often live traces are removed even though the archived trace
doesn't exist. This commit checkes the existence strictly.

Updates changed method names and fixes spec failures

Suggests to use a JSON structured log instead

Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102

This reverts merge request !27503

- Renames attributes from stat to project_statistiscs_name and attribute
to statistic_attribute
- Reordes methods on UpdateProjectStatistics concern
- Removes unused module from Ci::Build

We've already migrated all the legacy artifacts to the new realm,
which is ci_job_artifacts table.
It's time to remove the old code base that is no longer used.

Extracts combining the job_artifacts relation with the with_reports
scope for getting report artifacts into a method.

Immediate configuration is not ideal for group and instance
level clusters as projects that may never be deployed would
still have Kubernetes namespaces and service accounts created
for them.

As of https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/25586
we now create only the resources that are required for the
project being deployed, at the time of deployment.

With Pipelines for Merge Requests feature, users cannout keep using
$CI_COMMIT_REF_NAME and _SLUG predefined variables for dynamic
environments. We fix this problem by explicitly looking at the source
ref.

Alessio Caiazza authored 5 years ago and Douwe Maan committed 5 years ago

Refactor existing tests as a shared example

See which tests break

This backports the changes from
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10452

Legacy artifacts have been correctly migrated to new place -
ci_job_artifacts. Now it's time to remove the related code, but before
that we should ensure it doesn't break anything by using feature flag.

By using `refs/merge-requests/:iid/head`

ok

ok

Improve naming nicely

Add nice tests

add nice tests

fix some more

revert

The flag is on by default, but allows us to revert back
to the old behaviour if we encounter any problems.

Introduces the concept of Prerequisites for a CI build.
If a build has unmet prerequisites it will go through the
:preparing state before being made available to a runner.

There are no actual prerequisites yet, so current
behaviour is unchanged.

This style change enforces `return if ...` instead of
`return nil if ...` to save maintainers a few minor review points

Kamil Trzcińśki authored 6 years ago and Grzegorz Bizon committed 6 years ago

This makes code to support encrypted runner tokens.
This code also finished previously started encryption
process.

This commits extract code responsible for calculating essential CI/CD
variables to a separate concern. This makes it possible to share this
code between a `Ci::Build` and a `Ci::Bridge`.

We might want to refactor this to use composition instead of
inheritance.