Add ability to have the Jenkins Job Builder specify a script and
property file to use to inject environment variables into builds.
Change-Id: I628753ea526735e950b9d17697a08df1b412604f
Reviewed-on: https://review.openstack.org/12382
Approved: James E. Blair <corvus@inaugust.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
Change-Id: I94abedc07e0e5884cd737975c65d53375c598f14
Reviewed-on: https://review.openstack.org/11501
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Approved: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
Change-Id: I4d6312e92dffd596ae58e55c837e3db3ea7d1c52
Reviewed-on: https://review.openstack.org/11198
Reviewed-by: Monty Taylor <mordred@inaugust.com>
Approved: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
Switch to using entry points for loading modules as well as
individual buliders, triggers, publishers, etc.
Remove most openstack-specific python code.
Change templating so it's less repetitive -- a single project
definition will suffice for multiple jobs or job-groups.
This outputs XML that is identical to the current production XML,
warts and all. There are significant improvements that can be made
to the YAML in a separate change, as they will cause minor changes
to existing jobs (adding timestamps, logrotate, etc.). These are
mostly marked with TODO in this change.
Change-Id: Idcfddb3b43b6cfef4b20919a84540706d7a0a0b1
Reviewed-on: https://review.openstack.org/11000
Approved: James E. Blair <corvus@inaugust.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
Clark Boylan
James E. Blair