All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] travis: Temporary workaround for pull rate limit
Date: Mon, 18 Jan 2021 17:55:56 +0800	[thread overview]
Message-ID: <60055B2C.1080607@cn.fujitsu.com> (raw)
In-Reply-To: <20210118081350.21418-1-pvorel@suse.cz>

Hi Petr
I think using gcr.io mirror as a temporary solution is OK. But why we
not migrate into Github Actions directly? Now, it is time to this
release and do we should apply it before release?

Best Regards
Yang Xu
> Use mirror.gcr.io mirror to temporary workaround pull rate limit in
> docker registry. Correct solution is to migrate to Github Actions.
> 
> See also: #761
> 
> Signed-off-by: Petr Vorel<pvorel@suse.cz>
> ---
> Hi,
> 
> not a final solution for #761, just to get Travis quickly working.
> 
> Kind regards,
> Petr
> 
>   .travis.yml | 8 ++++++++
>   1 file changed, 8 insertions(+)
> 
> diff --git a/.travis.yml b/.travis.yml
> index edf627c33..245b790de 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -85,6 +85,14 @@ matrix:
> 
>   before_install:
>       - df -hT
> +    # pull rate limit workaround
> +    - tmpdaemon=$(mktemp)
> +    - sudo jq '."registry-mirrors" += ["https://mirror.gcr.io"]' /etc/docker/daemon.json>  $tmpdaemon
> +    - sudo mv $tmpdaemon /etc/docker/daemon.json
> +    - sudo systemctl daemon-reload
> +    - sudo systemctl restart docker
> +    - docker system info
> +    # ltp
>       - DIR="/usr/src/ltp"
>       - printf "FROM $DISTRO\nRUN mkdir -p $DIR\nWORKDIR $DIR\nCOPY . $DIR\n">  Dockerfile
>       - cat Dockerfile




  reply	other threads:[~2021-01-18  9:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18  8:13 [LTP] [PATCH 1/1] travis: Temporary workaround for pull rate limit Petr Vorel
2021-01-18  9:55 ` Yang Xu [this message]
2021-01-18 10:35   ` Petr Vorel
2021-01-18 11:38     ` Cyril Hrubis
2021-01-18 13:46       ` Petr Vorel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=60055B2C.1080607@cn.fujitsu.com \
    --to=xuyang2018.jy@cn.fujitsu.com \
    --cc=ltp@lists.linux.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.