make release job validation based on project type
Require puppet repositories to have the puppet jobs and node repositories to have the node jobs. Update the allowed values for release-type to include "puppet" and "nodejs" for folks who want to be explicit, but also use the module type-detection code to default properly. Report any jobs that are valid release jobs but for the wrong release type as errors instead of warnings. Change-Id: I9330cc62834f42ae0cd4d1cc48ed963846d72944 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
10
README.rst
10
README.rst
@@ -409,6 +409,16 @@ The top level of a deliverable file is a mapping with keys:
|
||||
``fuel``
|
||||
The Fuel project manages its own packages.
|
||||
|
||||
``puppet``
|
||||
All puppet modules should use this. If no release-type is
|
||||
specified and the validation job can determine that a module is a
|
||||
puppet module, it assumes a release-type of ``puppet``.
|
||||
|
||||
``nodejs``
|
||||
All nodejs modules should use this. If no release-type is
|
||||
specified and the validation job can determine that a module is a
|
||||
nodejs module, it assumes a release-type of ``nodejs``.
|
||||
|
||||
``releases``
|
||||
A list of the releases for the deliverable.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user