Citing Ian Wienand in [2]
"There was a thread some time ago that suggested coverage jobs weren't
doing much in the "post" pipeline because nobody looks at them and the
change numbers may be difficult to find anyway [1]. This came up again
in a cleanup to add non-voting coverage jobs in
I5c42530d1dda41b8dc8c13cdb10458745bec7bcc.
There really is no consistency across projects; it seems like a couple
of different approaches have been cargo-cult copied as new projects came
in, depending on which random project was used as a template. This
change does a cleanup by moving all post coverage jobs into the check
queue as non-voting jobs."
I've updated Ian's change [2] now and propose to move ahead with it -
and suggest that projects with in-repo coverage job follow it as well.
Let's use the new template [3] openstack-cover-jobs (and it's
-horizon/-neutron variants) for this change.
Andreas
[1] http://lists.openstack.org/pipermail/openstack-dev/2016-July/099491.html
[2] https://review.openstack.org/#/c/432836/
[3]
https://docs.openstack.org/infra/openstack-zuul-jobs/project-templates.html#project_template-openstack-cover-jobs
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
