Re: [rdo-list] [CI] proposal to change a job name
RDO is a community project to begin with and being pedantic, needing
to add a community word in there is a bit weird.
Can we have better descriptions for the jobs instead so it explains
better what's the role of each pipeline ?
I'll go on an obviously exaggerated tangeant and say that we could
always name the job:
"rdo-if-these-9-jobs-pass-we-will-promote-the-trunk-repositories-based-on-community-testing"
But I mean.. providing that kind of information and insight about what
the job is meant to be doing exactly is more the role of the
description and/or documentation IMO.
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Wed, Jan 11, 2017 at 11:11 PM, Wesley Hayutin <whayutin(a)redhat.com> wrote:
Greetings,
There seems to be quite a bit of confusion regarding the purpose of the jobs
in the public rdo ci system.
The naming conventions in these jobs are not very clear and it's
understandable that people have mixed things up a bit.
I propose we change the name of [1], to read
"rdo-delorean-promote-master-community"
This change would reflect that the job [1] is using the criteria set by the
rdo community for a rdo release of a build.
The rdo community expects openstack-puppet, packstack and tripleo to all be
validated for rdo releases and I think that *is*
appropriate for the community.
This would delineate and highlight the difference between other jobs that
are used as criteria for a particular installer like tripleo.
Thanks, let me know if you approve or have other suggestions.
[1]
https://ci.centos.org/view/rdo/view/promotion-pipeline/job/rdo-delorean-p...
_______________________________________________
rdo-list mailing list
rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com