Skip to content

Changes

Page history
Update gitlab autodevops authored by Jani Purujoki's avatar Jani Purujoki
Show whitespace changes
Inline Side-by-side
gitlab-autodevops.md
View page @ b7dc490d
...@@ -62,7 +62,7 @@ docker exec -it gitlab bash -c 'gitlab-ctl restart' ...@@ -62,7 +62,7 @@ docker exec -it gitlab bash -c 'gitlab-ctl restart'
Also it seems like that if you are trying to install Helm Tiller too fast after cluster is build you may face following error and you need to just wait couple of minutes, refresh and try installing again: Also it seems like that if you are trying to install Helm Tiller too fast after cluster is build you may face following error and you need to just wait couple of minutes, refresh and try installing again:
![helm_api_error](https://gitlab.labranet.jamk.fi/Mysticons/core/uploads/5c7be466e8a9edee0fd64bb260cd44ea/helm_api_error.png) ![helm_api_error](/uploads/6eaee047e500151d343883dba2179f73/helm_api_error.png)
## SSL settings ## SSL settings
You can automatically fetch certificate for GitLab omnibus by following official guide [here](https://docs.gitlab.com/omnibus/settings/ssl.html). You can automatically fetch certificate for GitLab omnibus by following official guide [here](https://docs.gitlab.com/omnibus/settings/ssl.html).
...@@ -85,24 +85,24 @@ To enable autodevops for GitLab follow the official guide [here](https://docs.gi ...@@ -85,24 +85,24 @@ To enable autodevops for GitLab follow the official guide [here](https://docs.gi
1. If your registry is not working correctly your build will fail at push stage. Check that you have done [Container Registry domain configuration](#container-registry-domain-configuration) 1. If your registry is not working correctly your build will fail at push stage. Check that you have done [Container Registry domain configuration](#container-registry-domain-configuration)
![image](/uploads/07f5df2ab9a22b0bf8c00f13d1f3c9d2/image.png) ![build_issue](/uploads/42b958cddb3bfbca4c5c995227001fbf/build_issue.png)
### Production issues ### Production issues
1. If your production fails: 1. If your production fails:
![image](/uploads/1cc68509c4fea91d4240bc763339bfa7/image.png) ![production_issue](/uploads/27f38ed12e97fb1abeb17242363d4b94/production_issue.png)
* You can disable Auto Devops from Settings -> CI/CD: * You can disable Auto Devops from Settings -> CI/CD:
![image](/uploads/60e5acf099994cf1552c3a89dd14595b/image.png) ![autodevops_disable](/uploads/d73b020f30b629a220bcd2f126439b21/autodevops_disable.png)
* Choose `CI/CD configuration` from your project and: * Choose `CI/CD configuration` from your project and:
* Choose template: .gitlab-ci.yml * Choose template: .gitlab-ci.yml
* Apply a template: Auto-DevOps * Apply a template: Auto-DevOps
* Edit line 45 to use your domain: * Edit line 45 to use your domain:
![image](/uploads/6274a11260a4c47cacb84dab6c65c0b9/image.png) ![autodevops_domain](/uploads/1aada97bfd84a173a283f4e5b034f81f/autodevops_domain.png)
### Container scanner issues ### Container scanner issues
...@@ -111,14 +111,14 @@ To enable autodevops for GitLab follow the official guide [here](https://docs.gi ...@@ -111,14 +111,14 @@ To enable autodevops for GitLab follow the official guide [here](https://docs.gi
* You can follow [Production issues](#production-issues) set up to modify your `.gitlab-ci.yml`. * You can follow [Production issues](#production-issues) set up to modify your `.gitlab-ci.yml`.
* Edit lines 472 and 473 to use `localhost:6060` instead of `docker:6060`: * Edit lines 472 and 473 to use `localhost:6060` instead of `docker:6060`:
![image](/uploads/b4c8b6fb63895db3a910b945b4223720/image.png) ![container_scanner_issue](/uploads/db64b4b5c412bc980857546fa2401988/container_scanner_issue.png)
### End result ### End result
* If everything is working you should be able to run the pipeline and pass every test expect performance. (It didn't work with gitlab.com either) * If everything is working you should be able to run the pipeline and pass every test expect performance. (It didn't work with gitlab.com either)
![image](/uploads/e56212aa6fe602a702b8dd2ad612e0e0/image.png) ![end_result](/uploads/238b17fcb0378f13b0d7bf8c9dc66870/end_result.png)
* Performance error: * Performance error:
![image](/uploads/c8782499c1ff55222d70acb76fa4d3fc/image.png) ![performance_issue](/uploads/b948f74274eeea093fa0d62e064d9fc2/performance_issue.png)
\ No newline at end of file \ No newline at end of file