Commit 1304e123 authored by Amy Qualls's avatar Amy Qualls

Merge branch '30933-docs-aqualls-final-issues' into 'master'

Docs: fix out of date Auto DevOps items

Closes #30933

See merge request gitlab-org/gitlab!32795
parents 759d4d37 a6723ebf
...@@ -393,9 +393,6 @@ To add a different cluster for each environment: ...@@ -393,9 +393,6 @@ To add a different cluster for each environment:
1. Navigate to your project's **{cloud-gear}** **Operations > Kubernetes**. 1. Navigate to your project's **{cloud-gear}** **Operations > Kubernetes**.
1. Create the Kubernetes clusters with their respective environment scope, as 1. Create the Kubernetes clusters with their respective environment scope, as
described from the table above. described from the table above.
![Auto DevOps multiple clusters](img/autodevops_multiple_clusters.png)
1. After creating the clusters, navigate to each cluster and install Helm Tiller 1. After creating the clusters, navigate to each cluster and install Helm Tiller
and Ingress. Wait for the Ingress IP address to be assigned. and Ingress. Wait for the Ingress IP address to be assigned.
1. Make sure you've [configured your DNS](#auto-devops-base-domain) with the 1. Make sure you've [configured your DNS](#auto-devops-base-domain) with the
...@@ -408,35 +405,6 @@ and verifying your application is deployed as a Review App in the Kubernetes ...@@ -408,35 +405,6 @@ and verifying your application is deployed as a Review App in the Kubernetes
cluster with the `review/*` environment scope. Similarly, you can check the cluster with the `review/*` environment scope. Similarly, you can check the
other environments. other environments.
## Currently supported languages
Note that not all buildpacks support Auto Test yet, as it's a relatively new
enhancement. All of Heroku's
[officially supported languages](https://devcenter.heroku.com/articles/heroku-ci#supported-languages)
support Auto Test. The languages supported by Heroku's Herokuish buildpacks all
support Auto Test, but notably the multi-buildpack does not.
As of GitLab 10.0, the supported buildpacks are:
```plaintext
- heroku-buildpack-multi v1.0.0
- heroku-buildpack-ruby v168
- heroku-buildpack-nodejs v99
- heroku-buildpack-clojure v77
- heroku-buildpack-python v99
- heroku-buildpack-java v53
- heroku-buildpack-gradle v23
- heroku-buildpack-scala v78
- heroku-buildpack-play v26
- heroku-buildpack-php v122
- heroku-buildpack-go v72
- heroku-buildpack-erlang fa17af9
- buildpack-nginx v8
```
If your application needs a buildpack that is not in the above list, you
might want to use a [custom buildpack](customize.md#custom-buildpacks).
## Limitations ## Limitations
The following restrictions apply. The following restrictions apply.
......
...@@ -152,8 +152,6 @@ these steps to enable Auto DevOps if it's disabled: ...@@ -152,8 +152,6 @@ these steps to enable Auto DevOps if it's disabled:
After you save your changes, GitLab creates a new pipeline. To view it, go to After you save your changes, GitLab creates a new pipeline. To view it, go to
**{rocket}** **CI/CD > Pipelines**. **{rocket}** **CI/CD > Pipelines**.
![First pipeline](img/guide_first_pipeline_v12_3.png)
In the next section, we explain what each job does in the pipeline. In the next section, we explain what each job does in the pipeline.
## Deploy the application ## Deploy the application
...@@ -167,7 +165,7 @@ without refreshing the page to **{status_success}** (for success) or ...@@ -167,7 +165,7 @@ without refreshing the page to **{status_success}** (for success) or
The jobs are separated into stages: The jobs are separated into stages:
![Pipeline stages](img/guide_pipeline_stages_v12_3.png) ![Pipeline stages](img/guide_pipeline_stages_v13_0.png)
- **Build** - The application builds a Docker image and uploads it to your project's - **Build** - The application builds a Docker image and uploads it to your project's
[Container Registry](../../user/packages/container_registry/index.md) ([Auto Build](stages.md#auto-build)). [Container Registry](../../user/packages/container_registry/index.md) ([Auto Build](stages.md#auto-build)).
...@@ -182,8 +180,8 @@ The jobs are separated into stages: ...@@ -182,8 +180,8 @@ The jobs are separated into stages:
- The `dependency_scanning` job checks if the application has any dependencies - The `dependency_scanning` job checks if the application has any dependencies
susceptible to vulnerabilities and is allowed to fail susceptible to vulnerabilities and is allowed to fail
([Auto Dependency Scanning](stages.md#auto-dependency-scanning-ultimate)) **(ULTIMATE)** ([Auto Dependency Scanning](stages.md#auto-dependency-scanning-ultimate)) **(ULTIMATE)**
- The `sast` job runs static analysis on the current code to check for potential - Jobs suffixed with `-sast` run static analysis on the current code to check for potential
security issues and is allowed to fail ([Auto SAST](stages.md#auto-sast-ultimate)) **(ULTIMATE)** security issues, and are allowed to fail ([Auto SAST](stages.md#auto-sast-ultimate)) **(ULTIMATE)**
- The `license_management` job searches the application's dependencies to determine each of their - The `license_management` job searches the application's dependencies to determine each of their
licenses and is allowed to fail licenses and is allowed to fail
([Auto License Compliance](stages.md#auto-license-compliance-ultimate)) **(ULTIMATE)** ([Auto License Compliance](stages.md#auto-license-compliance-ultimate)) **(ULTIMATE)**
...@@ -191,12 +189,17 @@ The jobs are separated into stages: ...@@ -191,12 +189,17 @@ The jobs are separated into stages:
NOTE: **Note:** NOTE: **Note:**
All jobs except `test` are allowed to fail in the test stage. All jobs except `test` are allowed to fail in the test stage.
- **Review** - Pipelines on `master` include this stage with a `dast_environment_deploy` job.
To learn more, see [Dynamic Application Security Testing (DAST)](../../user/application_security/dast/index.md).
- **Production** - After the tests and checks finish, the application deploys in - **Production** - After the tests and checks finish, the application deploys in
Kubernetes ([Auto Deploy](stages.md#auto-deploy)). Kubernetes ([Auto Deploy](stages.md#auto-deploy)).
- **Performance** - Performance tests are run on the deployed application - **Performance** - Performance tests are run on the deployed application
([Auto Browser Performance Testing](stages.md#auto-browser-performance-testing-premium)). **(PREMIUM)** ([Auto Browser Performance Testing](stages.md#auto-browser-performance-testing-premium)). **(PREMIUM)**
- **Cleanup** - Pipelines on `master` include this stage with a `stop_dast_environment` job.
After running a pipeline, you should view your deployed website and learn how After running a pipeline, you should view your deployed website and learn how
to monitor it. to monitor it.
......
...@@ -84,11 +84,39 @@ Auto Test runs the appropriate tests for your application using ...@@ -84,11 +84,39 @@ Auto Test runs the appropriate tests for your application using
your project to detect the language and framework. Several languages and your project to detect the language and framework. Several languages and
frameworks are detected automatically, but if your language is not detected, frameworks are detected automatically, but if your language is not detected,
you may be able to create a [custom buildpack](customize.md#custom-buildpacks). you may be able to create a [custom buildpack](customize.md#custom-buildpacks).
Check the [currently supported languages](index.md#currently-supported-languages). Check the [currently supported languages](#currently-supported-languages).
Auto Test uses tests you already have in your application. If there are no Auto Test uses tests you already have in your application. If there are no
tests, it's up to you to add them. tests, it's up to you to add them.
### Currently supported languages
Note that not all buildpacks support Auto Test yet, as it's a relatively new
enhancement. All of Heroku's
[officially supported languages](https://devcenter.heroku.com/articles/heroku-ci#supported-languages)
support Auto Test. The languages supported by Heroku's Herokuish buildpacks all
support Auto Test, but notably the multi-buildpack does not.
The supported buildpacks are:
```plaintext
- heroku-buildpack-multi
- heroku-buildpack-ruby
- heroku-buildpack-nodejs
- heroku-buildpack-clojure
- heroku-buildpack-python
- heroku-buildpack-java
- heroku-buildpack-gradle
- heroku-buildpack-scala
- heroku-buildpack-play
- heroku-buildpack-php
- heroku-buildpack-go
- buildpack-nginx
```
If your application needs a buildpack that is not in the above list, you
might want to use a [custom buildpack](customize.md#custom-buildpacks).
## Auto Code Quality **(STARTER)** ## Auto Code Quality **(STARTER)**
Auto Code Quality uses the Auto Code Quality uses the
......
...@@ -150,7 +150,7 @@ By now you should see the pipeline running, but what is it running exactly? ...@@ -150,7 +150,7 @@ By now you should see the pipeline running, but what is it running exactly?
To navigate inside the pipeline, click its status badge (its status should be "Running"). To navigate inside the pipeline, click its status badge (its status should be "Running").
The pipeline is split into a few stages, each running a couple of jobs. The pipeline is split into a few stages, each running a couple of jobs.
![Pipeline stages](../autodevops/img/guide_pipeline_stages_v12_3.png) ![Pipeline stages](../autodevops/img/guide_pipeline_stages_v13_0.png)
In the **build** stage, the application is built into a Docker image and then In the **build** stage, the application is built into a Docker image and then
uploaded to your project's [Container Registry](../../user/packages/container_registry/index.md) ([Auto Build](../autodevops/stages.md#auto-build)). uploaded to your project's [Container Registry](../../user/packages/container_registry/index.md) ([Auto Build](../autodevops/stages.md#auto-build)).
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment