On Sep 28, 2019, at 12:37 PM, kyrylo.shatskyy <kyrylo.shatskyy@suse.com> wrote:

It depends which code you mean. There is nothing in common between ’suite-repo’ and ’suite-branch’, they are not used for building rpm. The code of ceph components which are buildable is one thing, the code of tests is another thing.

If you are just modifying qa/tasks it is more likely related to the code of tests which is not required to build rebuilt on shaman to be delivered to test environment. And thus you can use --sha1 option for pointing the ceph builds and --suite-repo and --suite-branch to the tip of your branch. There is another option "--suite-relpath" which allows you to take a definition of the test from you local machine, but it does take to the code of tests to the teuthology worker. So your only choice is to push changes

to  github but still continue to use sha1 of previous builds.

On Sep 28, 2019, at 9:05 AM, Jos Collin <jcollin@redhat.com> wrote:

Hi Everyone,

How can I make teuthology-suite command to fetch the code from my local machine (laptop) and create a few jobs for me to test the code changes in qa/tasks/? This would save a lot of time when I work on qa/tasks/, as shaman would normally take 4-5 hrs to build. I tried changing --suite-repo and --suite-branch, but it always points to shaman.

Thanks,
Jos Collin
_______________________________________________
Dev mailing list -- dev@ceph.io
To unsubscribe send an email to dev-leave@ceph.io

_______________________________________________
Dev mailing list -- dev@ceph.io
To unsubscribe send an email to dev-leave@ceph.io