Skip to main content
aboutsummaryrefslogtreecommitdiffstats
blob: 1d677a9eddaf9fe83f580a9cce610782242306bf (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
<!-- **************************************************************************
#
# Copyright (C) 2004-2011 Oracle Corporation
#
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Eclipse Public License v1.0
# which accompanies this distribution, and is available at
# http://www.eclipse.org/legal/epl-v10.html
#
# Contributors:
#         Kohsuke Kawaguchi, Anton Kozak
#
#************************************************************************** -->

<div>
  Sometimes a project can only be successfully built on a particular slave
  (or master).  If so, this option forces Hudson to always build this project
  on a specific computer.

  If there is a group of machines that the job can be built on, you can specify
  that label as the node to tie on, which will cause Hudson to build the
  project on any of the machines with that label.

  <p>
  Otherwise, uncheck the box so that Hudson can schedule builds on available
  nodes, which results in faster turn-around time.

  <p>
  This option is also useful when you'd like to make sure that a project can
  be built on a particular node.
  <p>
  It's possible to use Project cascading feature for this property. Please review <a href="http://wiki.hudson-ci.org/display/HUDSON/Project+cascading">
  this document</a>.
</div>

Back to the top