commit | 4adf5c50d0eee0db14a4d69cd69ae62b41d53b1e | [log] [tgz] |
---|---|---|
author | Paul Belanger <pabelanger@redhat.com> | Sun Oct 30 21:38:13 2016 -0400 |
committer | Paul Belanger <pabelanger@redhat.com> | Wed Nov 09 12:18:39 2016 -0500 |
tree | c8b9714f60ba7092e44f0e00cb30cf3958dc901e | |
parent | 15e3e20936ddc2ae58f73e6be86a327be45c4373 [diff] |
Delete test_single_nonexistent_post_job test This is basically testing the case where Zuul wants to tell Jenkins to run a job, but Jenkins doesn't know about it. This doesn't really have an analog in a Zuul v3 world, where we no longer have that division. Adding a job to a pipeline with no job definition is really just a configuration error that we should catch in validation. Change-Id: I8f9cc063e0bd6472fbc78740279f51280f34ea64 Signed-off-by: Paul Belanger <pabelanger@redhat.com>