From f62dc5169984fc9ef29359659a428d2963a3ffc5 Mon Sep 17 00:00:00 2001 From: Andrew Schoen Date: Wed, 28 Oct 2015 10:19:05 -0500 Subject: [PATCH] ceph-setup-next should request a huge trusty node We've updated our tagging scheme, so now this job should request a slave that's tagged with both 'huge' and 'trusty'. Signed-off-by: Andrew Schoen --- ceph-setup-next/config/definitions/ceph-setup-next.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ceph-setup-next/config/definitions/ceph-setup-next.yml b/ceph-setup-next/config/definitions/ceph-setup-next.yml index 787af6ad..340e63dd 100644 --- a/ceph-setup-next/config/definitions/ceph-setup-next.yml +++ b/ceph-setup-next/config/definitions/ceph-setup-next.yml @@ -3,7 +3,7 @@ description: "This job step checks out the branch and builds the tarballs, diffs, and dsc that are passed to the ceph-build step.\r\n\r\nNotes:\r\nJob needs to run on a releatively recent debian system. The Restrict where run feature is used to specifiy an appropriate label.\r\nThe clear workspace before checkout box for the git plugin is used." # we do not need to pin this to trusty anymore for the new jenkins instance # FIXME: unpin when this gets ported over - node: trusty + node: huge && trusty disabled: false display-name: 'ceph-setup-next' concurrent: false -- 2.47.3