Next

After our recent resource usage changes, the CI requests had actually
become larger than our defaults.

This was added to the review job, but missed from stable, causing master
to fail

Enabled the operator in CI. Initial run.

- Add detection for CRD existing
- If CRD doesn't exist, `OPERATOR_BOOTSTRAP=true deploy` before `deploy`
  - If OPERATOR_BOOTSTRAP is not empty, then don't `--wait`
  - Also do this if `previousDeployFailed`, as this will clean up prior
    to the creation of the CRD.
- Add `crd` and `gitlabs` to `cleanup()`'s list of objects, if CRD exists

- Otherwise the runner page will fail, as the token from the backup was
encrypted with a different db_key_base

This adds the `kubernetes: active` selector for selected environments, which allows for testing in forks with an active kubernetes integration.

 Forks with no kubernetes integration will no longer have failing tests due to the 'variables' artifact not being injected by the previous stages.
  This is a rudimentary solution to the basic issue of being unable expect to run helm on forks / share integrations with forks.

  Fixes charts/gitlab#835

Reordering the jobs so that functions defined in `auto_devops` template can
be used in specs jobs also.

This should do a better job of removing the test jobs, that have been
cluttering up our UI.

This also has the added benefit of allowing us to retry these, which
wasn't working before.

The newest version of the gem doesn't work with tests prior to the 11.3
codebase

Better solutions are being looked at here: https://gitlab.com/gitlab-org/gitlab-ce/issues/49134

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

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

Most MRs should have a changelog item, all MR's should have
an assignee, proper description and additional metadata.

To match changes made in the upstream qa gem

See: gitlab-org/gitlab-qa!151 and
gitlab-org/gitlab-qa!157

Which only runs for branches and not for tags

release-tools

In order for the release-tools update to work, we need at least one
changelog with the new syntax. So I've gone and left the pre 0.2.0
changes as our weekly ones, and have changed the post 0.2.0 to the
versioned syntax.

I will completely remove the changelog code from this repo after we've
seen a release compeletly work with the new changelog handling.

[ci skip]

Using latest was a mistake

This reverts merge request !368

And can also be run manually

Read today in the docs that the stop review needs to happen in the same
stage as the deploy: https://docs.gitlab.com/ee/ci/yaml/#environment-action

This appears to at least fix the issue of being able to manually call
stop.

update to the new syntax as introduced here: gitlab-org/gitlab-qa!143