[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v4 3/4] Jobs based on custom runners: docs and gitlab-runner
From: |
Erik Skultety |
Subject: |
Re: [PATCH v4 3/4] Jobs based on custom runners: docs and gitlab-runner setup playbook |
Date: |
Tue, 20 Oct 2020 09:00:42 +0200 |
On Mon, Oct 19, 2020 at 04:54:50PM -0400, Cleber Rosa wrote:
> On Mon, Oct 19, 2020 at 12:26:10PM +0200, Erik Skultety wrote:
> > On Sun, Oct 18, 2020 at 09:50:02PM -0400, Cleber Rosa wrote:
> > > +
> > > + - name: Checks the availability of official gitlab-runner builds in
> > > the archive
> > > + uri:
> > > + url: https://s3.amazonaws.com/gitlab-runner-downloads/v{{
> > > gitlab_runner_version }}/binaries/gitlab-runner-linux-386
> > > + method: HEAD
> > > + status_code:
> > > + - 200
> > > + - 403
> >
> > Why is 403 an acceptable success status code?
> >
>
> I missed this question in my last reply, sorry.
>
> s3 will throw a 403 if the URI doesn't exist... and we don't want to fail
> the playbook because of that, given that we'll attempt the fallback
> repo defined in vars.yml{,.template}.
Right, forgot about the repo in vars.yml fallback, thanks for explaining.
Regards,
Erik
[PATCH v4 2/4] Jobs based on custom runners: build environment docs and playbook, Cleber Rosa, 2020/10/18
Re: [PATCH v4 2/4] Jobs based on custom runners: build environment docs and playbook, Andrea Bolognani, 2020/10/20
Re: [PATCH v4 2/4] Jobs based on custom runners: build environment docs and playbook, Thomas Huth, 2020/10/21
[PATCH v4 4/4] Jobs based on custom runners: add job definitions for QEMU's machines, Cleber Rosa, 2020/10/18