mirror of
https://gitlab.com/buildroot.org/buildroot.git
synced 2026-09-09 16:01:54 -09:00
f4ffe6a721
From [1]:
"In November 2020, Docker introduced rate limits on pull requests from
Docker Hub [2]. If your GitLab CI/CD configuration uses an image from
Docker Hub, each time a job runs, it may count as a pull request."
Since then, some jobs in our gitlab-ci fail when this rate limits is
reached [3].
To avoid this rate limit, move our Docker image from dockerhub to the
registry provided by gitlab. Keeping the image from dockerhub would be
possible by using dependency proxy [4] but the gitlab registry is good
enough.
Tested on gitlab:
https://gitlab.com/kubu93/buildroot/-/jobs/1694863584
[1] https://docs.gitlab.com/ee/user/packages/container_registry/index.html
[2] https://docs.docker.com/docker-hub/download-rate-limit/
[3] https://gitlab.com/buildroot.org/buildroot/-/jobs/1687590417
[4] https://docs.gitlab.com/ee/user/packages/dependency_proxy
Signed-off-by: Romain Naour <romain.naour@gmail.com>
Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
(cherry picked from commit b3b4e270d1)
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
24 lines
584 B
YAML
24 lines
584 B
YAML
# Configuration for Gitlab-CI.
|
|
# Builds appear on https://gitlab.com/buildroot.org/buildroot/pipelines
|
|
|
|
image: $CI_REGISTRY/buildroot.org/buildroot/base:20211120.1925
|
|
|
|
stages:
|
|
- generate-gitlab-ci
|
|
- build
|
|
|
|
generate-gitlab-ci-yml:
|
|
stage: generate-gitlab-ci
|
|
script: ./support/scripts/generate-gitlab-ci-yml support/misc/gitlab-ci.yml.in > generated-gitlab-ci.yml
|
|
artifacts:
|
|
paths:
|
|
- generated-gitlab-ci.yml
|
|
|
|
buildroot-pipeline:
|
|
stage: build
|
|
trigger:
|
|
include:
|
|
- artifact: generated-gitlab-ci.yml
|
|
job: generate-gitlab-ci-yml
|
|
strategy: depend
|