Auto DevOps

Auto DevOps is a technology that allows automated application of DevOps best practices.

Current end-to-end tests

At the time of writing this entry there are two end-to-end test files:

under the qa/specs/features/browser_ui/7_configure folder of the qa directory. There are not presently any end-to-end api-based tests.

Where the tests execute

Non-quarantined test execution environments

The Configure AutoDevOps Templates template: express|rails|spring works with Auto DevOps test is a tagged to run only in the :staging environment and therefore runs in :

  • staging -qa-triggers-browser_ui-7_configure

Quarantined tests

The following tests, if they are tagged quarantine, will run in these environments:

Configure AutoDevOps Templates template: express|rails|spring works with Auto DevOps

  • staging
    • qa-triggers-browser_ui-quarantine

Configure your GDK to run the tests

Follow the documentation on how to Use GDK with a GKE cluster.

NOTE: The default instructions below prescribe using “the GCP project called gitlab-internal-153318 for development and testing,” which, in order to create a cluster on said project, requires a set of permissions your humble author did not possess, whereas I have found that using the project gitlab-qa-resources was more compliant with my permission set.

Run the tests

To run the create_project_with_auto_devops_spec tests, ensure you have GDK set up to run a GKE cluster (see above instructions) and call the test from the ../gitlab/qa/ directory.

Example: CHROME_HEADLESS=true bundle exec bin/qa Test::Instance::All http://gdk.test:3000 -- qa/specs/features/browser_ui/7_configure/auto_devops/create_project_with_auto_devops_spec.rb --tag orchestrated --tag kubernetes

or

gitlab-qa Test::Instance::Image EE -- qa/specs/features/browser_ui/7_configure/auto_devops/create_project_with_auto_devops_spec.rb --tag orchestrated --tag kubernetes to run orchestrated.

To run the auto_devops_templates_spec.rb tests, it is easiest to execute the tests against the staging environment by following these instructions for setting up your environment variables. NOTE: You will need access to the “QA Vault” in 1password. If you require access, you can fill out an individual access request from here

Example: gitlab-qa Test::Instance::Staging -- qa/specs/features/browser_ui/7_configure/auto_devops/auto_devops_templates_spec.rb to run orchestrated (append --tag quarantine to run quarantined tests)

* For information as to why we’re running master pipelines on qa-mirror see the following issues:

Last modified March 20, 2024: fix: Update links to "End User Services". (a68c0e2d)
View page source - Edit this page - please contribute. Creative Commons License