Gitlab CI/CD
Guides/tips...etc
- Issue Study:
- docker cli tools in .gitlab-ci.yml:
- Enable Docker commands in your CI/CD jobs
- The shell executor
- Docker-in-Docker
- Docker socket binding
- Enable Docker commands in your CI/CD jobs
- Java CI task in Gitlab CI:
- Bash定時任務腳本執行期間剛好與開發人員執行的CI任務產生資源競爭,造成彼此無法順利完成
- 可能解決方式:
- 暫時: 先錯過定時任務的執行時間,避免資源競爭
- 比較好的方式:
- 可在原本的.gitlab-ci.yml中加入定時任務的清理腳本
- 也可以在定時任務的清理腳本中,加入webhook與gitlab API互動,確定哪些條件下,清理腳本必需執行
- 或者棄用原本的Shell executor,改用docker executor,達成Clean build environment for every build的效果
- 可能解決方式:
- docker cli tools in .gitlab-ci.yml:
- GitLab
- Runner execution flow
- docs.gitlab.com/17.9/ci/yaml/
- docs.gitlab.com/runner/executors/
- Enable Docker commands in your CI/CD jobs
- runner
- Kubernetes executor
- Using GitLab CI/CD with a GitHub repository
- Tutorial: Scan a Docker container for vulnerabilities
- Test with GitLab CI/CD and generate reports in merge requests
- Monitor GitLab Runner usage
- Go tools and GitLab: How to do continuous integration like a boss
- Convert Jenkins configuration to GitLab CI/CD
- How to use GitLab CI/CD for Vue.js