In case when `needs:` is missing, but when requested by service,
we would not save the pipeline with config_error.

This makes it explicit that we want to persist the error
as `config_error` failure reason.

This allows overriding `only.refs` to something else if needed. 

mdhtr authored 5 years ago and Nick Thomas committed 5 years ago

as requested by the reviewer

Previously the following syntax would fail in the linter with an
error 500:

```
include:
  template:
    - License-Management.gitlab-ci.yml
    - Dependency-Scanning.gitlab-ci.yml
    - SAST.gitlab-ci.yml
```

Now the error will call out specifically that the value
is not a string.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66605

These services aren't specific to GCP, and will be used for AWS
as part of https://gitlab.com/gitlab-org/gitlab-ce/issues/46686

Ensure the evaluation of right-hand side expression always
results in the returning of an object or an empty String

This is a port from EE changes where
we introduce a new limit for Plan model.

https://dev.gitlab.org/gitlab/gitlab-ee/merge_requests/1182

- Added Gitlab::Ci::Config::Entry::Rules and Gitlab::Ci::Config::Entry::Rules:Rule
  to handle lists of Rule objects to be evalauted for job inclusion
- Added `if:` and `changes:` as available Rules::Rule::Clause classes
- Added Rules handling logic to Seed::Build#included? with extra specs
- Use DisallowedKeysValidator to mutually exclude rules: from only:/except: on job config

This makes to limit `needs:` to 5 by default.
Allow to increase the limit to 50 with disable of FF.

This changes the `needs:` logic to require
that all jobs to be present. Instead of skipping
do fail the pipeline creation if `needs:` dependency
is not found.

Since we are unsure what would be the behavior of `stage:`
when we work on DAG. Let's make `stage:` to be required
today with `needs:`.

In the job log adds a highlight when hovering
the collapsible line

In the job log, if the user clicks the section title
the job log section will be collapsed

Tiger Watson authored 5 years ago and Thong Kuah committed 5 years ago

Kubernetes deployments on new clusters will now have
a separate namespace per project environment, instead
of sharing a single namespace for the project.

Behaviour of existing clusters is unchanged.

All new functionality is controlled by the
:kubernetes_namespace_per_environment feature flag,
which is safe to enable/disable at any time.

Ports changes from
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/12343

This changes `needs:` from weak reference
to have a strong reference.

This means that job will not be created
unless all needs are present as part of
a pipeline.

Currently we write out empty CSS classes (`class=""`) every time we
create a new tag. This adds 9 unnecessary bytes per span element. In a
recent trace, I have counted 11950 span elements. So we transported 105
unnecessary kilobytes!

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

Default dependency job stage index to Infinity, and correctly report it as undefined in prior stages

Add project scope

We dropped MySQL support and a lot of mysql specific code has been
removed in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/29608.

This comes in from the other direction and removes any `if postgresql?`
branches.

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

Convert several occurrences of `map` + `flatten` to
`flat_map` where applicable.

https://gitlab.com/gitlab-org/cluster-integration/auto-deploy-image

https://gitlab.com/gitlab-org/gitlab-ce/issues/65019

https://gitlab.com/gitlab-org/gitlab-ce/issues/65019

James Keogh authored 5 years ago and Thong Kuah committed 5 years ago

Rename changelog to correct issue number, be more explicit that we're talking about Auto DevOps projects

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

Fabien Catteau authored 5 years ago and Mayra Cabrera committed 5 years ago

Propagate PIP_INDEX_URL, PIP_EXTRA_INDEX_URL
to the dependency-scanning Docker image
to support Python projects depending on custom
Pypi registries. These variables will be consumed
by the gemnasium-python analyzer.

Keep feature flag disabled by default and turn off
all functionality related to legacy triggers.

* Block legacy triggers from creating pipeline
* Highlight legacy triggers to be invalid via the UI
* Make legacy triggers invalid in the model