[PATCH 0/2] automation: build in an openSUSE Leap container.

[PATCH 0/2] automation: build in an openSUSE Leap container.

[Dario Faggioli]

Hello,

This series adds the dockerfile for openSUSE Leap (latest version, 15
at the time of writing), as well as the gitlab CI runes for building
the project inside it.

I've tested locally building xen, tools, docs, etc, in a container
generated from the provided dockerfile with both gcc and clang.

I've also pushed the container to our registry, and there's a run
currently pending here:

 https://gitlab.com/xen-project/people/dfaggioli/xen/pipelines/36897573

(Not sure if the fact that it hasn't started yet is my fault... :-/ )

The patches are also available in the following git branches:

 https://gitlab.com/dfaggioli/xen/tree/rel/ci/opensuse-leap-v1
 git://xenbits.xen.org/people/dariof/xen.git rel/ci/opensuse-leap-v1

It's pretty much the first time I play with this Docker thing, so
apologies if something is glaringly wrong. :-P

Regards,
Dario
---
Dario Faggioli (2):
      automation: add openSUSE Leap dockerfile.
      automation: build on openSUSE Leap.

 .gitlab-ci.yml                                 |   32 +++++++++++
 automation/build/suse/opensuse-leap.dockerfile |   67 ++++++++++++++++++++++++
 2 files changed, 99 insertions(+)
 create mode 100644 automation/build/suse/opensuse-leap.dockerfile
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

[PATCH 1/2] automation: add openSUSE Leap dockerfile.

[Dario Faggioli]

Tracks the latest releast of openSUSE Leap. At the time of writing this
patch, this is Leap 15.

Signed-off-by: Dario Faggioli <dfaggioli@suse.com>
---
Cc: Doug Goldstein <cardoe@cardoe.com>
Cc: Wei Liu <wei.liu2@citrix.com>
---
 automation/build/suse/opensuse-leap.dockerfile |   67 ++++++++++++++++++++++++
 1 file changed, 67 insertions(+)
 create mode 100644 automation/build/suse/opensuse-leap.dockerfile

diff --git a/automation/build/suse/opensuse-leap.dockerfile b/automation/build/suse/opensuse-leap.dockerfile
new file mode 100644
index 0000000000..614a5c8405
--- /dev/null
+++ b/automation/build/suse/opensuse-leap.dockerfile
@@ -0,0 +1,67 @@
+FROM opensuse/leap
+LABEL maintainer.name="The Xen Project" \
+      maintainer.email="xen-devel@lists.xenproject.org"
+
+ENV USER root
+
+RUN mkdir /build
+WORKDIR /build
+
+RUN zypper ref && zypper up -y
+RUN zypper install -y \
+        acpica \
+        bc \
+        bin86 \
+        bison \
+        bzip2 \
+        checkpolicy \
+        clang \
+        cmake \
+        dev86 \
+        discount \
+        flex \
+        gcc \
+        gettext-tools \
+        git \
+        glib2-devel \
+        glibc-devel \
+        glibc-devel-32bit \
+        gzip \
+        hostname \
+        libSDL2-devel \
+        libaio-devel \
+        libbz2-devel \
+        libext2fs-devel \
+        libgnutls-devel \
+        libjpeg62-devel \
+        libnl3-devel \
+        libnuma-devel \
+        libpixman-1-0-devel \
+        libpng16-devel \
+        libssh2-devel \
+        libtasn1-devel \
+        libuuid-devel \
+        libyajl-devel \
+        lzo-devel \
+        make \
+        nasm \
+        ncurses-devel \
+        ocaml \
+        ocaml-findlib-devel \
+        ocaml-ocamlbuild \
+        ocaml-ocamldoc \
+        pandoc \
+        patch \
+        pkg-config \
+        python \
+        python-devel \
+        systemd-devel \
+        tar \
+        transfig \
+        valgrind-devel \
+        wget \
+        which \
+        xz-devel \
+        zlib-devel \
+        && \
+        zypper clean


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [PATCH 1/2] automation: add openSUSE Leap dockerfile.

[Wei Liu]

On Fri, Nov 16, 2018 at 07:31:02PM +0100, Dario Faggioli wrote:
> Tracks the latest releast of openSUSE Leap. At the time of writing this
> patch, this is Leap 15.
> 
> Signed-off-by: Dario Faggioli <dfaggioli@suse.com>

Acked-by: Wei Liu <wei.liu2@citrix.com>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

[PATCH 2/2] automation: build on openSUSE Leap.

[Dario Faggioli]

Signed-off-by: Dario Faggioli <dfaggioli@suse.com>
---
Cc: Doug Goldstein <cardoe@cardoe.com>
Cc: Wei Liu <wei.liu2@citrix.com>
---
 .gitlab-ci.yml |   32 ++++++++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index a3b393fade..815e626291 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -323,3 +323,35 @@ debian-unstable-gcc-debug-arm64:
     XEN_TARGET_ARCH: arm64
   tags:
     - arm64
+
+opensuse-leap-clang:
+  <<: *build
+  variables:
+    <<: *clang
+    CONTAINER: suse:opensuse-leap
+    debug: n
+    XEN_TARGET_ARCH: x86_64
+
+opensuse-leap-clang-debug:
+  <<: *build
+  variables:
+    <<: *clang
+    CONTAINER: suse:opensuse-leap
+    debug: y
+    XEN_TARGET_ARCH: x86_64
+
+opensuse-leap-gcc:
+  <<: *build
+  variables:
+    <<: *gcc
+    CONTAINER: suse:opensuse-leap
+    debug: n
+    XEN_TARGET_ARCH: x86_64
+
+opensuse-leap-gcc-debug:
+  <<: *build
+  variables:
+    <<: *gcc
+    CONTAINER: suse:opensuse-leap
+    debug: y
+    XEN_TARGET_ARCH: x86_64


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [PATCH 2/2] automation: build on openSUSE Leap.

[Wei Liu]

On Fri, Nov 16, 2018 at 07:31:10PM +0100, Dario Faggioli wrote:
> Signed-off-by: Dario Faggioli <dfaggioli@suse.com>

Acked-by: Wei Liu <wei.liu2@citrix.com>

I would like to rearrange your code a bit to move it above the
arm builds.

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [PATCH 2/2] automation: build on openSUSE Leap.

[Dario Faggioli]

[-- Attachment #1.1: Type: text/plain, Size: 678 bytes --]

On Fri, 2018-11-16 at 18:42 +0000, Wei Liu wrote:
> On Fri, Nov 16, 2018 at 07:31:10PM +0100, Dario Faggioli wrote:
> > Signed-off-by: Dario Faggioli <dfaggioli@suse.com>
> 
> Acked-by: Wei Liu <wei.liu2@citrix.com>
> 
> I would like to rearrange your code a bit to move it above the
> arm builds.
> 
Sure, that indeed makes sense.

Lemme know if you'd do it when committing, or you want me to.

Thanks and Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [PATCH 0/2] automation: build in an openSUSE Leap container.

[Wei Liu]

On Fri, Nov 16, 2018 at 07:30:55PM +0100, Dario Faggioli wrote:
> Hello,
> 
> This series adds the dockerfile for openSUSE Leap (latest version, 15
> at the time of writing), as well as the gitlab CI runes for building
> the project inside it.
> 
> I've tested locally building xen, tools, docs, etc, in a container
> generated from the provided dockerfile with both gcc and clang.
> 
> I've also pushed the container to our registry, and there's a run
> currently pending here:
> 
>  https://gitlab.com/xen-project/people/dfaggioli/xen/pipelines/36897573
> 
> (Not sure if the fact that it hasn't started yet is my fault... :-/ )

I have been playing with the CI system today so it could have been a bit
overwhelmed. Let's wait until next week to see if it comes back.

As far as I can tell the Arm64 builds are already done.

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [PATCH 0/2] automation: build in an openSUSE Leap container.

[Dario Faggioli]

[-- Attachment #1.1: Type: text/plain, Size: 937 bytes --]

On Fri, 2018-11-16 at 18:44 +0000, Wei Liu wrote:
> On Fri, Nov 16, 2018 at 07:30:55PM +0100, Dario Faggioli wrote:
> >  
> > https://gitlab.com/xen-project/people/dfaggioli/xen/pipelines/36897573
> > 
> > (Not sure if the fact that it hasn't started yet is my fault... :-/ 
> > )
> 
> I have been playing with the CI system today so it could have been a
> bit
> overwhelmed. Let's wait until next week to see if it comes back.
> 
Ok, sure. What I'm most interested, is to see if the opensuse jobs pass
(i.e., if I got the rune, the name of the container, etc, right :-) ).

> As far as I can tell the Arm64 builds are already done.
> 
Ah, yes, now they are.

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [PATCH 0/2] automation: build in an openSUSE Leap container.

[Dario Faggioli]

[-- Attachment #1.1: Type: text/plain, Size: 1332 bytes --]

On Fri, 2018-11-16 at 19:50 +0100, Dario Faggioli wrote:
> On Fri, 2018-11-16 at 18:44 +0000, Wei Liu wrote:
> > On Fri, Nov 16, 2018 at 07:30:55PM +0100, Dario Faggioli wrote:
> > > 
> > I have been playing with the CI system today so it could have been
> > a
> > bit
> > overwhelmed. Let's wait until next week to see if it comes back.
> > 
> Ok, sure. What I'm most interested, is to see if the opensuse jobs
> pass
> (i.e., if I got the rune, the name of the container, etc, right :-)
> ).
> 
And... it worked! :-)

Now, the next step would be to add openSUSE Tumbleweed too.

But I have a question, Tumbleweed is rolling (and it's actually rolling
quite fast); how can we handle that?

I'd say the container image should be rebuild (or, at least, the
'package refresh && package update' bits of the dockerfile be re-
executed), if not at every run of the pipeline, frequently enough. Can
we do that?

I see that we have Debian unstable, which is also rolling, but do we
actually update it, or is it, basically, just a snapshot?

Thanks and Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [PATCH 0/2] automation: build in an openSUSE Leap container.

[Doug Goldstein]

> On Nov 16, 2018, at 3:41 PM, Dario Faggioli <dfaggioli@suse.com> wrote:
> 
>> On Fri, 2018-11-16 at 19:50 +0100, Dario Faggioli wrote:
>>> On Fri, 2018-11-16 at 18:44 +0000, Wei Liu wrote:
>>>> On Fri, Nov 16, 2018 at 07:30:55PM +0100, Dario Faggioli wrote:
>>>> 
>>> I have been playing with the CI system today so it could have been
>>> a
>>> bit
>>> overwhelmed. Let's wait until next week to see if it comes back.
>>> 
>> Ok, sure. What I'm most interested, is to see if the opensuse jobs
>> pass
>> (i.e., if I got the rune, the name of the container, etc, right :-)
>> ).
>> 
> And... it worked! :-)
> 
> Now, the next step would be to add openSUSE Tumbleweed too.
> 
> But I have a question, Tumbleweed is rolling (and it's actually rolling
> quite fast); how can we handle that?
> 
> I'd say the container image should be rebuild (or, at least, the
> 'package refresh && package update' bits of the dockerfile be re-
> executed), if not at every run of the pipeline, frequently enough. Can
> we do that?
> 
> I see that we have Debian unstable, which is also rolling, but do we
> actually update it, or is it, basically, just a snapshot?

It’s basically a snapshot. We could create a pipeline to rebuild containers periodically. 
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [PATCH 0/2] automation: build in an openSUSE Leap container.

[Dario Faggioli]

[-- Attachment #1.1: Type: text/plain, Size: 1337 bytes --]

On Fri, 2018-11-16 at 16:51 -0600, Doug Goldstein wrote:
> > On Nov 16, 2018, at 3:41 PM, Dario Faggioli <dfaggioli@suse.com>
> > wrote:
> > 
> > But I have a question, Tumbleweed is rolling (and it's actually
> > rolling
> > quite fast); how can we handle that?
> > 
> > I'd say the container image should be rebuild (or, at least, the
> > 'package refresh && package update' bits of the dockerfile be re-
> > executed), if not at every run of the pipeline, frequently enough.
> > Can
> > we do that?
> > 
> > I see that we have Debian unstable, which is also rolling, but do
> > we
> > actually update it, or is it, basically, just a snapshot?
> 
> It’s basically a snapshot. 
>
Ok.

> We could create a pipeline to rebuild containers periodically. 
>
Right. If that's doable, then I'll just prepare another dockerfile for
Tumbleweed (will be very similar to this one, although probably not
identical... I'll see about sharing/consolidating, but can't promise).

And then we do the rebuilding pipeline trick, at least for the images
of rolling distros.

Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [PATCH 0/2] automation: build in an openSUSE Leap container.

[Wei Liu]

On Sat, Nov 17, 2018 at 12:07:28AM +0100, Dario Faggioli wrote:
> On Fri, 2018-11-16 at 16:51 -0600, Doug Goldstein wrote:
> > > On Nov 16, 2018, at 3:41 PM, Dario Faggioli <dfaggioli@suse.com>
> > > wrote:
> > > 
> > > But I have a question, Tumbleweed is rolling (and it's actually
> > > rolling
> > > quite fast); how can we handle that?
> > > 
> > > I'd say the container image should be rebuild (or, at least, the
> > > 'package refresh && package update' bits of the dockerfile be re-
> > > executed), if not at every run of the pipeline, frequently enough.
> > > Can
> > > we do that?
> > > 
> > > I see that we have Debian unstable, which is also rolling, but do
> > > we
> > > actually update it, or is it, basically, just a snapshot?
> > 
> > It’s basically a snapshot. 
> >
> Ok.
> 
> > We could create a pipeline to rebuild containers periodically. 
> >
> Right. If that's doable, then I'll just prepare another dockerfile for
> Tumbleweed (will be very similar to this one, although probably not
> identical... I'll see about sharing/consolidating, but can't promise).
> 
> And then we do the rebuilding pipeline trick, at least for the images
> of rolling distros.

We should do that for all distros, because even the stable ones do point
releases from time to time.

Your series is now pushed, BTW.

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel