All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mykola Golub <to.my.trociny@gmail.com>
To: Sage Weil <sweil@redhat.com>
Cc: ceph-devel@vger.kernel.org, "sepia@ceph.com" <sepia@ceph.com>
Subject: Re: [sepia] how to use teuthology-suite in the new world
Date: Thu, 15 Dec 2016 16:51:44 +0200	[thread overview]
Message-ID: <20161215145143.GA1451@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1612142211440.10615@piezo.novalocal>

Hi, Sage,

It looks like we still need to push testing branches to ceph.git for
things like below?

qa/workunits/rbd/test_librbd_python.sh:

wget -O test_rbd.py "https://git.ceph.com/?p=ceph.git;a=blob_plain;hb=$CEPH_REF;f=src/test/pybind/test_rbd.py" || \
    wget -O test_rbd.py "https://git.ceph.com/?p=ceph.git;a=blob_plain;hb=ref/heads/$CEPH_REF;f=src/test/pybind/test_rbd.py"

Do we have some env variable (CEPH_REPO?) we could use simirlaly to
CEPH_REF here?

On Wed, Dec 14, 2016 at 10:22:31PM +0000, Sage Weil wrote:
> Please read carefully if you use teuthology:
> 
> ceph-qa-suite.git is no more.  All tests are now in qa/tasks, qa/suite, 
> and so on.  The directory structure is the same (but now prefixed with 
> qa/) and the git history is intact.
> 
> If you have any pull requests outstanding against ceph-qa-suite, you'll 
> need to redo them as a pull-request against ceph.git.
> 
> Jenkins + shaman will build packages for both ceph.git and ceph-ci.git.
> 
> You should only push official branches (master, kraken, jewel, etc.) to 
> ceph.git.
> 
> You should only push a branch to ceph-ci.git if you need packages built.  
> I suggest
> 
>   git remote add ci git@github.com:ceph/ceph-ci
> 
> Teuthology now defaults to https://github.com/ceph/ceph-ci.git instead of 
> ceph.git.
> 
> To schedule a test against something in ceph-ci.git,
> 
>   teuthology-suite -s rados -c wip-foo
> 
> To schedule against something in ceph.git (e.g., master),
> 
>   teuthology-suite -s rados -c master --ceph-repo https://github.com/ceph/ceph.git
> 
> In both of these cases, the tests (tasks/ and suite/ yamls) are taken from 
> the same repo and branch that we used to resolve your branch name to a 
> sha1 (shaman builds are identified by sha1).
> 
> To schedule a test against a suite branch that is different from the ceph 
> branch you can use --suite-repo and --suite-branch.  For example,
> 
>   teuthology-suite -s rados -c wip-mybuild \
> 	--suite-repo https://github.com/liewegas/ceph.git \
> 	--suite-branch wip-my-updated-test-case
> 
> This is not new, but if you want teuthology-suite to find the most recent 
> build for a branch (useful when master is moving quickly but you just need 
> a recent build) you can use -n <max # commits to backtrack>:
> 
>   teuthology-suite -s rados -c master \
> 	--ceph-repo https://github.com/ceph/ceph.git \
> 	-n 10
> 
> sage
> _______________________________________________
> Sepia mailing list
> Sepia@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/sepia-ceph.com

-- 
Mykola Golub

  parent reply	other threads:[~2016-12-15 14:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14 22:22 how to use teuthology-suite in the new world Sage Weil
2016-12-14 22:27 ` Sage Weil
2016-12-15 14:51 ` Mykola Golub [this message]
2016-12-15 15:00   ` [sepia] " Mykola Golub
2016-12-15 15:46     ` John Spray
2016-12-15 15:54       ` Jason Dillaman
2016-12-15 16:04         ` John Spray
2016-12-15 16:11           ` Sage Weil
2016-12-15 16:12           ` Jason Dillaman
     [not found]             ` <CALe9h7fXGBwcWE0hpk5Bvw6RSpKtqRdUQiUOBf-SXGjrc0L+fg@mail.gmail.com>
2016-12-15 22:32               ` Sage Weil
2016-12-15 17:15           ` Vasu Kulkarni
2016-12-22 22:12 ` Nathan Cutler
2016-12-22 22:21   ` 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=20161215145143.GA1451@gmail.com \
    --to=to.my.trociny@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sepia@ceph.com \
    --cc=sweil@redhat.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.