On Wed, Feb 14, 2018 at 12:06 AM, Paul Belanger <pabelan...@redhat.com> wrote:
> On Tue, Feb 13, 2018 at 11:05:34PM +0900, gmann wrote:
>> Hi Infra Team,
>> I have 1 quick question on zuulv3 jobs and their migration part. From
>> zuulv3 doc , it is clear about migrating the job definition and use
>> those among cross repo pipeline etc.
>> But I did not find clear recommendation that whether project's
>> pipeline definition should stay in project-config or we should move
>> that to project side.
>> 'template' part(which has system level jobs) can stay in
>> project-config. For example below part-
>> Other pipeline definition- 'check', 'gate', 'experimental' etc should
>> be move to project repo, mainly this list-
>> If we move those past as mentioned above then, we can have a
>> consolidated place to control the project pipeline for
>> 'irrelevant-files', specific branch etc
>> ..1 https://docs.openstack.org/infra/manual/zuulv3.html
> As it works today, pipeline stanza needs to be in a config project
> (project-config) repo. So what you are suggestion will not work. This was done
> to allow zuul admins to control which pipelines are setup / configured.
> I am mostly curious why a project would need to modify a pipeline
> or duplicate it into all projects, over having it central located in
pipeline stanza and configuration stay in project-config. I mean list
of jobs defined in each pipeline for specific project for example
here. Now we have list of jobs for each pipeline in 2 places, one
in project-config  and second in project repo.
Issue in having it in 2 places:
- No single place to check what all jobs project will run with what conditions
- If we need to modify the list of jobs in pipeline or change other
bits like irrelevant-files etc then it has to be done in
project-config. So no full control by project side.
>  https://docs.openstack.org/infra/zuul/user/config.html#pipeline
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
OpenStack Development Mailing List (not for usage questions)