Thanks, Sage. I am eager to use the new stuff, but ATM it appears that
Shaman does not build hammer at all.
See https://jenkins.ceph.com/job/ceph-dev-setup/4055//consoleFull
Right after configure it appears to do "git diff" and not like what it
sees. All hammer-based branches (including hammer itself) fail in the
same way.
Needless to say, in gitbuilder they build fine.
This is blocking work on the 0.94.10 release.
Nathan
On 12/14/2016 02:31 AM, Sage Weil wrote:
On Tue, 13 Dec 2016, Nathan Cutler wrote:
Hi Alfredo:
I'm trying to build a "wip-hammer-backports" integration branch to test the
0.94.10 release, but shaman doesn't like it for some reason:
https://jenkins.ceph.com/job/ceph-dev-setup/4002//consoleFull
The same branch passes gitbuilder. Could you take a look?
There is a new teuthology-suite option, --ceph-repo, that you can pass the
repo name to. So, for example,
teuthology-suite -s rados -c wip-foo --ceph-repo https://github.com/ceph/ceph-ci.git
Soon we'll switch the default around so that ceph-ci.git will be the
default and you'll need to tell teuthology-suite if you're scheduling
against a branch in ceph.git (this will mostly just be the cron jobs).
Also, starting very soon (tomorrow), --suite-repo will also pick up this
value, so that it is (by default) assumed that the *tests* will come out
of this repo too. That is, the default for --suite-repo will be whatever
--ceph-repo is, and --suite-relpath will default to 'qa' (the suite yaml
files will soon be merged into ceph.git qa/suite/*). --suite-branch
will continue to default to whatever the -c ceph branch is (like they do
already), although it will seem a bit less magic than before since it's
generally the same branch in the same repo.
sage
Thanks,
Nathan
On 12/12/2016 01:48 PM, Alfredo Deza wrote:
**REMINDER**
Please, push development branches to ceph-ci.git to get
repositories/binaries built.
We are scheduled to restrict permissions to ceph.git in a few days.
Thanks!
On Wed, Dec 7, 2016 at 7:34 AM, Alfredo Deza <adeza@xxxxxxxxxx> wrote:
As announced on November 23rd, please start pushing development
branches to ceph-ci.git (https://github.com/ceph/ceph-ci) to get
repositories.
This doesn't change reporting in https://shaman.ceph.com and it
shouldn't affect testing via teuthology.
The ceph.git repository will continue to build binaries and
repositories for another week to help transitioning.
If you have any issues, please mention them in the #sepia or
#ceph-devel channels to me (alfredodeza) or Andrew Schoen
(andrewschoen).
Thanks!
-Alfredo
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Nathan Cutler
Software Engineer Distributed Storage
SUSE LINUX, s.r.o.
Tel.: +420 284 084 037
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Nathan Cutler
Software Engineer Distributed Storage
SUSE LINUX, s.r.o.
Tel.: +420 284 084 037
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
