Open Stack

Hi Jerry,

Thanks for the solution it worked.

On Wed, Apr 15, 2015 at 3:47 PM, Jerry Zhao <xyzjerry at gmail.com> wrote:

>  jobs:
>   - name: ^dsvm-tempest.*$
>     parameter-function: reusable_node
>
>      branch: ^master.*$
>
> something like this.
>
>
>
> On 04/15/2015 03:03 AM, Abhishek Shrivastava wrote:
>
>  Hi Jerry,
>
>  Following is my layout.yaml file, can you please point out where and
> what changes to be put:
>
>  jobs:
>   - name: ^dsvm-tempest.*$
>     parameter-function: reusable_node
>
>  projects:
>   - name: openstack/cinder
>     check:
>       # Remove this after successfully verifying communication with
> upstream
>       # and seeing a posted successful review.
>       #- noop-check-communication
>       # Uncomment this job when you have a jenkins slave running and want
> to
>       # test a full Tempest run within devstack.
>       - dsvm-tempest-full
>
>
> On Wed, Apr 15, 2015 at 3:19 PM, Jerry Zhao <xyzjerry at gmail.com> wrote:
>
>>
>> http://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul/layout.yaml#n636
>>
>>   - name: ^(gate|check)-tempest-dsvm-neutron-full$
>>     branch: ^(?!stable/icehouse).*$
>>
>> This example will skip icehouse branch for the jobs that match the regexp.
>>
>>
>>
>>
>> On 04/15/2015 02:40 AM, Abhishek Shrivastava wrote:
>>
>>  I am using Zuul, so if can point me our about the filter then it would
>> be a great help.
>>
>> On Wed, Apr 15, 2015 at 3:07 PM, Jerry Zhao <xyzjerry at gmail.com> wrote:
>>
>>>  Are you using gerrit trigger plugin or zuul?
>>> There is a filter in either tool to refine jenkins job to a particular
>>> branch.
>>>
>>>
>>>
>>> On 04/15/2015 12:39 AM, Abhishek Shrivastava wrote:
>>>
>>>   Hi All,
>>>
>>>  In our CI I have been observing that, for any commits done in gerrit
>>> other than "*master branch*" the CI fails. This is because of the fact
>>> that our CloudByte driver code is present only in *master(kilo and
>>> further)* branch but not in *juno or icehouse. *
>>>
>>>  Are there any suggestions that I need to follow or ignore it & let it
>>> run the way it is running?
>>>
>>>  Here's a link of the patch for which the CloudByte CI failed:
>>>
>>>    - https://review.openstack.org/173697
>>>
>>>  --
>>>
>>>
>>> *Thanks & Regards, *
>>> *Abhishek*
>>>  *Cloudbyte Inc. <http://www.cloudbyte.com>*
>>>
>>>
>>>   _______________________________________________
>>> OpenStack-Infra mailing listOpenStack-Infra at lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>
>>>
>>>
>>
>>
>>  --
>>
>>
>> *Thanks & Regards, *
>> *Abhishek*
>>  *Cloudbyte Inc. <http://www.cloudbyte.com>*
>>
>>
>>
>
>
>  --
>
>
> *Thanks & Regards, *
> *Abhishek*
>  *Cloudbyte Inc. <http://www.cloudbyte.com>*
>
>
>


-- 


*Thanks & Regards,*
*Abhishek*
*Cloudbyte Inc. <http://www.cloudbyte.com>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20150415/1868175a/attachment.html>