removing the dynamic naming of the expected testplan 60/47860/1
authorJamo Luhrsen <jluhrsen@redhat.com>
Wed, 2 Nov 2016 21:44:55 +0000 (14:44 -0700)
committerJamo Luhrsen <jluhrsen@redhat.com>
Wed, 2 Nov 2016 21:44:55 +0000 (14:44 -0700)
commit220339b50539ae0ccb4c78f52668174c759cd39f
tree9a91c36202d9c466ce835b80faf6abf254b5f706
parent6709044fc31c4d271bd829abaa6d0d17cf0e8d3f
removing the dynamic naming of the expected testplan

now that these jobs are using expanding functionalities (e.g. upstream vs gating)
but expecting those multiple jobs to still use the same set of robot suites, we
can pin these jobs to a single testplan file.  otherwise, we'd need to create
a bunch of duplicate testplan files.

Change-Id: If9def1ae8aa3b30095dc781e0a48197220dce9a0
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>
jjb/netvirt/netvirt-csit-1node-multi-openstack.yaml
jjb/netvirt/netvirt-csit-3node-multi-openstack.yaml
jjb/netvirt/netvirt-legacy-csit-1node-multi-openstack.yaml
jjb/netvirt/netvirt-legacy-csit-3node-multi-openstack.yaml