From: "Vasilev, Oleg" <oleg.vasilev@intel.com>
To: "Hiler, Arkadiusz" <arkadiusz.hiler@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH v2 3/3] gitlab-ci: introduce final containers
Date: Fri, 23 Aug 2019 12:41:03 +0000 [thread overview]
Message-ID: <af3d25f5f2cae2cf54774febfdab3215dca3531f.camel@intel.com> (raw)
In-Reply-To: <20190822084507.5ahepd54elkhbhwo@ahiler-mobl1.fi.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 2002 bytes --]
On Thu, 2019-08-22 at 11:45 +0300, Arkadiusz Hiler wrote:
> On Tue, Aug 20, 2019 at 04:19:36PM +0300, Oleg Vasilev wrote:
...
> >
> > +############## FINAL CONTAINERS ####################
> > +
> > +
> > +final-containers:igt-final:
>
> I am sceptical about having it named igt-final.
>
> How about just igt-x86_64?
>
> If you need further clarification on what people should use then you
> can
> add "build-env-" to the name of the *base* images.
Hi,
I could rename igt-final to igt and igt-* to igt-base-*. Would it break
any preexiting automatization?
>
> > + stage: final-containers
> > + image: docker:stable
> > + services:
> > + - docker:dind
> > + dependencies:
> > + - build:tests-fedora
> > + variables:
> > + DOCKER_HOST: tcp://docker:2375
> > + DOCKER_DRIVER: overlay2
> > + FORCE_REBUILD: 1
> > + script:
> > + - docker login -u gitlab-ci-token -p $CI_JOB_TOKEN
> > $CI_REGISTRY
> > + - docker pull $CI_REGISTRY/$CI_PROJECT_PATH/igt-fedora
> > + - docker tag $CI_REGISTRY/$CI_PROJECT_PATH/igt-fedora igt-
> > fedora
> > + - scripts/pull-or-rebuild.sh Dockerfile.final igt-final
> > diff --git a/Dockerfile.final b/Dockerfile.final
> > new file mode 100644
> > index 00000000..214a5c20
> > --- /dev/null
> > +++ b/Dockerfile.final
> > @@ -0,0 +1,16 @@
> > +# Version number to bump for force image rebuild: 0
> > +FROM igt-fedora
> > +
> > +RUN dnf install -y findutils && \
> > + dnf clean all
> > +
> > +COPY opt-igt /opt/igt
> > +COPY scripts/docker-help.sh /usr/local/bin/docker-help.sh
> > +
> > +ENV PATH="/opt/igt/bin:${PATH}"
> > +ENV
> > LD_LIBRARY_PATH="/opt/igt/lib:/opt/igt/lib64:${LD_LIBRARY_PATH}"
> > +ENV IGT_TEST_ROOT="/opt/igt/libexec/igt-gpu-tools"
> > +
> > +COPY scripts/docker-help.sh /usr/local/bin/docker-help.sh
>
> I would also put this one in .gitlab-ci/
This not technically CI-related, but docker-related. Why not leave it
in scripts/?
Oleg
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3261 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-08-23 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 13:19 [igt-dev] Add containers with IGT inside Oleg Vasilev
2019-08-20 13:19 ` [igt-dev] [PATCH v2 1/3] gitlab-ci: move containers section to the up Oleg Vasilev
2019-08-22 8:45 ` Arkadiusz Hiler
2019-08-20 13:19 ` [igt-dev] [PATCH v2 2/3] gitlab-ci: rebuild images only on Dockerfile changes Oleg Vasilev
2019-08-22 8:26 ` Arkadiusz Hiler
2019-08-20 13:19 ` [igt-dev] [PATCH v2 3/3] gitlab-ci: introduce final containers Oleg Vasilev
2019-08-22 8:45 ` Arkadiusz Hiler
2019-08-23 12:41 ` Vasilev, Oleg [this message]
2019-08-23 12:50 ` Arkadiusz Hiler
2019-08-23 12:56 ` Arkadiusz Hiler
2019-08-20 16:08 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [v2,1/3] gitlab-ci: move containers section to the up Patchwork
2019-08-20 23:48 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=af3d25f5f2cae2cf54774febfdab3215dca3531f.camel@intel.com \
--to=oleg.vasilev@intel.com \
--cc=arkadiusz.hiler@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox