A system to validate plugin parameters in jenkins job builder

[Khai Do]

I noticed that parameters defined in yaml files are not validated before getting passed to jenkins job builder (builder.py). It would be nice to setup a system to validate that the parameters are somewhat correct before getting used by jenkins job builder.

For example if we look at this line in copyartifact in builder.py:

   XML.SubElement(t, 'projectName').text = data["project"]

There might be 4 validations that can be done..
1. check that data["project"] is not null
2. check that data["project"] is not an empty string
3. check that data["project"] is a string type
4. check that jenkins actually has a project that matches data["project"]

The first 3 is pretty generic for every piece of data so maybe setup something that would let users specify that the data["project"] must be a string type, is required, and must not be an empty string when that data is defined.

So something like...

     builders:
         - copyartifact:
              project<isString, isRequired, isNotEmpty>: foo
              filter: *.tar.gz
              target: /home/foo
              which-build: specific-build
              build-number: 123

[James E. Blair (corvus)]

This could use voluptuous as zuul does.