From: Dan Mick <dmick@redhat.com>
To: "sepia@lists.ceph.com" <sepia@lists.ceph.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: teuthology-suite new feature: --newest [n]
Date: Thu, 23 Jun 2016 15:52:25 -0700 [thread overview]
Message-ID: <576C6829.4010204@redhat.com> (raw)
If you don't use teuthology-suite, you can stop reading now.
I've added a new option to teuthology-suite, --newest, that will modify
how searching for builds works.
Currently, you can specify -c/--ceph to name a Ceph branch or -S/--sha1
to name a specific commit. This chooses the version of Ceph that is
used to search for completed builds for the arch/distro/versions in your
run. The branchname is translated to a sha1 by looking up the branch on
a git server, and then the process is the same for both -c and -S: look
for that sha1 to have successfully built on all gitbuilders; if it
doesn't exist, the run fails.
With --newest, rather than failing, suite will try 'backtracking' along
the commit history of the branch/sha1, and searching for older commits
that have been built, backtracking as many times as you allow (by
default, 10 commits). So, for instance, if you specify "-c master
--newest", suite will search for a build corresponding to the current
HEAD of master, as usual, but, if not found, will then try HEAD^, and
HEAD^^, and so on up to HEAD~10. The newest commit that has a clean
build will be used for the run, and you'll see a log message about which
sha1 was chosen and how many commits older it was.
I expect this to be most-useful for nightly runs, but others may find it
useful as well. Please try it if you wish, and send questions, bugs,
comments etc. to me or to the sepia list.
--
Dan Mick
Red Hat, Inc.
Ceph docs: http://ceph.com/docs
next reply other threads:[~2016-06-23 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 22:52 Dan Mick [this message]
2016-06-24 12:22 ` teuthology-suite new feature: --newest [n] Sage Weil
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=576C6829.4010204@redhat.com \
--to=dmick@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sepia@lists.ceph.com \
/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.