It seems the file is truncated on Github preview. It stops at
openstack/security-specs

If you check the raw file[1], you will find entry of openstack/vitrage

[1]:
https://raw.githubusercontent.com/openstack-infra/project-config/master/zuul/layout.yaml


[image: Screen Shot 2017-01-05 at 9.11.08 AM.png]
<https://raw.githubusercontent.com/openstack-infra/project-config/master/zuul/layout.yaml>

On Thu, Jan 5, 2017 at 8:39 AM <[email protected]> wrote:

> Hi,
>
>
> I know. Why only python-vitrageclient and puppet-vitrage register in the
> zuul/layout.yaml? They also register in the jeknins/jobs/projects.yaml.
>
> And other vitrage projects only register in the
> jeknins/jobs/projects.yaml.
>
> I'm confused if i want to add a new jenkins job, which file should i
> register in?
>
>
> BR,
>
> dwj
>
>
>
>
>
> 原始邮件
> *发件人:*Weyl,Alexey(Nokia-IL)
> *收件人:*董文娟00101742;
> *抄送人:*<[email protected]>
> *日 期 :*2017年01月04日 19:13
> *主 题 :**RE: Re: [openstack-dev] [ALU]   [Vitrage] vitrage tempest job
> config*
>
>
> We do write code in the zuul/layout.yaml:
>
>   - name: openstack/puppet-vitrage
>
>     template:
>
>       - name: merge-check
>
>       - name: puppet-check-jobs
>
>       - name: puppet-module-unit-jobs
>
>       - name: puppet-beaker-jobs
>
>       - name: puppet-beaker-jobs-xenial
>
>       - name: puppet-branch-tarball-jobs
>
>       - name: openstack-server-release-jobs
>
>       - name: release-notes-jobs
>
>   - name: openstack/python-vitrageclient
>     template:
>       - name: merge-check
>       - name: python-jobs
>       - name: python35-jobs
>       - name: check-requirements
>       - name: publish-to-pypi
>       - name: osc-plugin-jobs
>
> Alexey
>
> From: [email protected] [mailto:[email protected]]
> Sent: Wednesday, January 04, 2017 10:59 AM
> To: Weyl, Alexey (Nokia - IL)
> Cc: [email protected]
> Subject: 答复: Re: [openstack-dev] [ALU] [Vitrage] vitrage tempest job config
>
> Hi Alexey,
>
>
> As far as i know, every project needs to register in the zuul/layout.yaml[1], 
> so zuul can submit the job to jenkins via gearman.
>
> So the jenkins knows which jobs need to run and then run the job which 
> defined in the jenkins/jobs/XXX.yaml.
>
> Did i missing something? Or the job registeration moved from zuul/layout.yaml 
> to jenkins/jobs/projects.yaml?
> If yes, how can zuul know which jobs need to submit to jenkins?Thanks~
>
> [1]
> https://github.com/openstack-infra/project-config/blob/master/zuul/layout.yaml
>
>
> BR,
> dwj
>
>
>
>
> 原始邮件
> 发件人:Weyl,Alexey(Nokia-IL)
> 收件人:OpenStack Development Mailing List (not for usage questions);
> 日 期 :2017年01月04日 16:30
> 主 题 :Re: [openstack-dev] [ALU]   [Vitrage] vitrage tempest job config
>
> Hi Dong,
>
>
> All of that data is configured the openstack-infra/project-config in github.
>
> There you can find our changes by searching for vitrage.
>
> The main files that we have pushed our changes are:
> jenkins/jobs/vitrage.yaml
> gerrit/projects.yaml
> jenkins/jobs/projects.yaml
>
> BR,
> Alexey
>
> From: [email protected] [mailto:[email protected]]
> Sent: Wednesday, January 04, 2017 9:49 AM
> To: [email protected]
> Subject: [ALU] [openstack-dev] [Vitrage] vitrage tempest job config
>
>
> Hi all,
>
> I didn't find any vitrage project jenkins jobs registered in zuul/layout.yaml.
> Where does all the jobs configed?Thanks~
> BR,
> dwj
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: [email protected]?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: [email protected]?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to