Re: [Xen-devel] [PATCH 2/3] automation: add openSUSE Tumbleweed CI image

2019-08-03 Thread Doug Goldstein

On 7/31/19 11:58 AM, Dario Faggioli wrote:


openSUSE comes in two flavours: Leap, which is non-rolling, and released
annualy, and Tumbleweed, which is rolling.

Reasons why it makes sense to have both (despite both being openSUSE,
package lists in dockerfiles being quite similar, etc) are:
- Leap share a lot with SUSE Linux Enterprise. So, regressions on Leap,
   not only means regressions for all openSUSE Leap users, but also helps
   prevent/catch regressions on SLE;
- Tumbleweed often has the most bleeding-edge software, so it will help
   us prevent/catch regressions with newly released versions of
   libraries, compilers, etc (e.g., at the time of writing this commit,
   some build issues, with GCC9, where discovered while trying to build
   in a Tumbleweed image).

Note that, considering the rolling nature of Tumbleweed, the container
would need to be rebuilt (e.g., periodically), even if the docker file
does not change.

Signed-off-by: Dario Faggioli 

Acked-by: Doug Goldstein 

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

[Xen-devel] [PATCH 2/3] automation: add openSUSE Tumbleweed CI image

2019-07-31 Thread Dario Faggioli
openSUSE comes in two flavours: Leap, which is non-rolling, and released
annualy, and Tumbleweed, which is rolling.

Reasons why it makes sense to have both (despite both being openSUSE,
package lists in dockerfiles being quite similar, etc) are:
- Leap share a lot with SUSE Linux Enterprise. So, regressions on Leap,
  not only means regressions for all openSUSE Leap users, but also helps
  prevent/catch regressions on SLE;
- Tumbleweed often has the most bleeding-edge software, so it will help
  us prevent/catch regressions with newly released versions of
  libraries, compilers, etc (e.g., at the time of writing this commit,
  some build issues, with GCC9, where discovered while trying to build
  in a Tumbleweed image).

Note that, considering the rolling nature of Tumbleweed, the container
would need to be rebuilt (e.g., periodically), even if the docker file
does not change.

Signed-off-by: Dario Faggioli 
---
Cc: Doug Goldstein 
Cc: Wei Liu 
---
 .../build/suse/opensuse-tumbleweed.dockerfile  |   68 
 1 file changed, 68 insertions(+)
 create mode 100644 automation/build/suse/opensuse-tumbleweed.dockerfile

diff --git a/automation/build/suse/opensuse-tumbleweed.dockerfile 
b/automation/build/suse/opensuse-tumbleweed.dockerfile
new file mode 100644
index 00..2676a87c85
--- /dev/null
+++ b/automation/build/suse/opensuse-tumbleweed.dockerfile
@@ -0,0 +1,68 @@
+FROM opensuse/tumbleweed
+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 --no-recommends
+RUN zypper install -y --no-recommends \
+acpica \
+bc \
+bin86 \
+bison \
+bzip2 \
+checkpolicy \
+clang \
+cmake \
+dev86 \
+discount \
+flex \
+gcc \
+gcc-c++ \
+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 -a


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