tree 8d5552d8862a46093bd3da56f55898af74761ec3
parent f166784a286643c3afda0057e0b787be869b2c14
author Monty Taylor <mordred@inaugust.com> 1474046128 -0400
committer Monty Taylor <mordred@inaugust.com> 1475192130 -0500
gpgsig -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1
 
 iQIcBAABCAAGBQJX7aVCAAoJEHuulLxxQaWUM9oQALEcBbgpMb3La1k/DmgeJu97
 3PG+biK6GfAHQ4S9BGseSphh54+LFQKO5ZDWOrJOcDgURyqt/vnzxTUCodoptcDy
 vAvZ/rjmcFW3opZ60ra74fNy2X0z/suj1d2KN/9MChvs+kNWY8emjvq9dVw9Zwy5
 pnvugIT9I66wSVbx91bQrv0Z5Ynzw+H3TnRMt+eNCTVqmIcw2ZVvfBGSYzZeloWj
 TgcJ8OsU/JY9VbCwsmnkMcU9GGRT4Jd5dSKFrS88xps/8U+xdvlPd/MWbY2cRexm
 0u6mrUAytg7RR3WpQJAgMF7TsPcSCC2df7zBv5jlWahd+trBHroxR7kKYu3y2N4E
 3rXyVZ7KKSxaNMN4ahYQsKmXiIuBWVqq1LLPPVqg1uXqo9Ws9miVzbxtVqyjcLNW
 V8JMMbQRjw1r/jzPRj0nHA2SOYDEQlvBCw2SYiLqgea8BePjpLkWbpf2fcDj8Zjd
 AMkbkA3K3WHzm5V6Gftlod8RD+Yesbo4P4C+heLRCZsaYhkZtpAjLcpT4QxAtqH5
 gfDjKWK2h4M3a7ImeWRAHSfN22lPrHvSxSeJLs1QOfLnyiaQfRR8flMOjAAKgIWo
 oPJDOxYYe5U3AoA5BQQEOygANmJvnrdFOgJCByBo0hqz4wMDZTHZd0h10pNSA4x/
 IQfqCV/BZfN4jA2fpGYR
 =jCia
 -----END PGP SIGNATURE-----

Split playbook into vars, pre-playbook and playbook

In order to get to the point where playbooks that people write for tests
are playbooks that they could conceivably also use outside of the zuul
context, we need to remove the need for zuul-specific things in the main
playbook.

Add a pre-playbook that runs before the playbook and runs the things
that are not tied to current JJB content - namely setting up the logger
and prepping directories.

Move the SUCCESS/FAILURE message to the post-playbook.

Extract the injected variables into a variables file and add a
-e@vars.yaml option to the playbook invocation. This provides variables
in a known namespace. Obviously there is still an exercise in how a user
might write a playbook that wants to consume those variables in some
way.

Change-Id: Ie5ec6ec65a03ceea9afc3ac59df73cb28f5ca4dd