Clark Boylan writes:
> Also reading these job defs and comparing against the zuulv3 spec it
> isn't clear to me what the expected behavior for inheriting pre and post
> playbooks is. Seems like maybe pre is a queue so parent pre roles run
> first and post is a stack so
On Wed, Mar 8, 2017, at 07:20 AM, Paul Belanger wrote:
>
> Greetings,
>
> Allow me to bring to your attention a series of patches which create our
> first
> zuulv3 jobs. Specifically, we are looking to discuss what a generic tox
> job in
> ansible will look like.
>
> Currently, we have 2
Thanks, Paul.
For me both have their strength and weaknesses:
* If you want to add a new tox job for an existing target like pep8, I
like how simple that is with
https://review.openstack.org/#/c/438281/25/.zuul.yaml
* On the other hand, if you add a new tox job - for a completely new
target,
Hi,
On 03/08/2017 09:45 PM, Paul Belanger wrote:
Ya, so far 438281 (multi-playbook) seems to be the front runner. But like you
said, none of this is set in stone. It is completely possible some time down the
road another option will be more valid.
I also vote for 438281 (multi-playbook). That
On Wed, Mar 08, 2017 at 12:03:21PM -0500, David Shrewsbury wrote:
> They're both fairly easy to understand. I think the multi-playbook option
> might make any customization that we might need to do later a bit easier,
> if that's something we foresee
> doing to these playbooks. If they're pretty
They're both fairly easy to understand. I think the multi-playbook option
might make any customization that we might need to do later a bit easier,
if that's something we foresee
doing to these playbooks. If they're pretty much set in stone as they are
though, I don't
think it will matter much
On Wed, Mar 08, 2017 at 10:20:23AM -0500, Paul Belanger wrote:
>
> Greetings,
>
> Allow me to bring to your attention a series of patches which create our first
> zuulv3 jobs. Specifically, we are looking to discuss what a generic tox job in
> ansible will look like.
>
> Currently, we have 2
Greetings,
Allow me to bring to your attention a series of patches which create our first
zuulv3 jobs. Specifically, we are looking to discuss what a generic tox job in
ansible will look like.
Currently, we have 2 proposed patches for zuul (feature/zuulv3) branch
available:
Generic tox (single