It's sometimes required to trigger a job build on every CI message.
To achieve that the XML's noSquash (jjb: no-squash) has to be set to
True.

see triggers section at:
https://wiki.jenkins.io/display/JENKINS/JMS+Messaging+Plugin

Change-Id: I389e59cca4f649379614f7f6247bf76cf4a0ba95

In the new version of PyYAML the API changed to be more explicit. Now
the default value for the Loader is None, see:

https://github.com/yaml/pyyaml/blob/5.1/lib3/yaml/__init__.py#L103

The load is unsafe. It's better to use safe_load function.

Change-Id: Ia1cd16f2ff970ca220a266c99b6554dd4254ebd9

The spam caused by jjb not doing anything with a job is not
generally interesting so switch it to a DEBUG level logger.

Change-Id: I0c5277612c8db3a11a1e44d4855b4a51226a8f2c
Signed-off-by: Thanh Ha <zxiiro@gmail.com>

It's helpful to have possibility to set `jobAlias` in case the
same job is used multiple times with different configurations.

Change-Id: Ic092c6b2f5d893e75ebce4aaebc7eaf88a8978a6

Updated gerrit trigger support to include the new exclude private and
exclude wip changes.

Change-Id: I75d8113941e4e455ec34fab23d347816c2ef699b

Ensure that we can resolve any lazily loaded templates that might be
dictionary keys in yaml. For more informmation please see the added test
case in tests/yamlparser/fixtures/jinja-string04.yaml.

Change-Id: I67fbca422f2165729af15e4d039278ad66f6240b
Story: 2006431
Task: 36338

Jinja templates are not deep-copyable so they cannot be used in
"defautls" sections or to pick defualts for job groups or projects.

This works around the issue by waiting until we render the template to
construct the template itself.

Story: 2006431
Task: 36337
Change-Id: Ief31fdaac06bb14d0aaba71c8c0e658a7f861671

It's nowadays opendev.org so use that.

Change-Id: I91382e8d18deec6c91e84d9232f013792631e66a