Sage Weil 5f5eb2b241 upgrade*: do not hard-code next as the final upgrade hop ... The overrides for the job will have some branch; leave the target unspecified so that we use that as the target version. This will let us test upgrades to master and next (and whatever else, provided it is a forward hop). Signed-off-by: Sage Weil <sage@inktank.com>		2013-10-16 16:06:37 -07:00
..
0-cluster	upgrade: add rados-double suite (bobtail -> cuttlefish -> next)	2013-06-23 21:58:30 -07:00
1-bobtail-install	upgrade: add rados-double suite (bobtail -> cuttlefish -> next)	2013-06-23 21:58:30 -07:00
2-bobtail-workload	upgrade: add rados-double suite (bobtail -> cuttlefish -> next)	2013-06-23 21:58:30 -07:00
3-upgrade	modified upgrade tasks to run from cuttlefish to dumpling, dumpling to next	2013-08-14 13:15:37 -07:00
4-restart	upgrade: ignore mds restart order on rbd, rados tests	2013-07-01 16:09:45 -07:00
5-dumpling-workload	added workunit: branch:dumpling wherever applicable	2013-08-14 15:53:29 -07:00
6-upgrade-next	upgrade*: do not hard-code next as the final upgrade hop	2013-10-16 16:06:37 -07:00
7-restart	upgrade: ignore mds restart order on rbd, rados tests	2013-07-01 16:09:45 -07:00
8-next-workload	upgrade*: do not hard-code next as the final upgrade hop	2013-10-16 16:06:37 -07:00
%	mark all existing collections with %	2013-08-28 11:24:29 -07:00