All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erwan Velu <evelu@redhat.com>
To: ceph-devel@vger.kernel.org
Subject: Little update on the build platform
Date: Tue, 31 May 2016 13:49:12 -0400 (EDT)	[thread overview]
Message-ID: <902296593.97770947.1464716952266.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1236727659.97766119.1464716235552.JavaMail.zimbra@redhat.com>

Hi folks,

Just a short email to mention several updates that have been pushed to the build platfrorm 
- build VMs are now generated by the edeploy (https://github.com/redhat-cip/edeploy) project
- centos 7, ubuntu {trusty|xenial} are now built with the same automated procedure
- xfs is becoming the default rootfs of those VMs
- build requires are already installed reducing the time required by install-deps.sh
- An diagnosis helper is now in place to spot known build failures  :
A list of common issues have been entered (like gcc or jenkins failures, segfaults, etc...)
A typical output looks like : https://jenkins.ceph.com/job/ceph-pull-requests/6448/
If you find new build failures, feel free to ping me to add them.
This helps at finding build issues in a second while the build logs are pretty long to read.

All that improvements are targeting a more reliable build system.

Please note that we have a lot of segfaults during the builds, if some can have a look around that would be lovely.

Erwan,

       reply	other threads:[~2016-05-31 17:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1236727659.97766119.1464716235552.JavaMail.zimbra@redhat.com>
2016-05-31 17:49 ` Erwan Velu [this message]
2016-05-31 17:58   ` Little update on the build platform Piotr Dałek
2016-05-31 18:02     ` Erwan Velu
2016-05-31 18:16       ` Piotr Dałek
2016-05-31 18:44   ` John Spray
2016-05-31 19:14     ` Ken Dreyer
2016-06-01 14:40       ` Erwan Velu
2016-06-01 14:57         ` Sage Weil
2016-06-02  8:11   ` Nathan Cutler
2016-06-13 15:41     ` Ken Dreyer

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=902296593.97770947.1464716952266.JavaMail.zimbra@redhat.com \
    --to=evelu@redhat.com \
    --cc=ceph-devel@vger.kernel.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 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.