Making steps stick with a server

Steps within a project can run on different servers if their selectors allow it. But you may want all or most of the steps of a project to run on the same server, whether or not you specify that server in advance. The project-level Sticky property gives you that option.

To view project-level properties, select Projects, and then click the Edit icon Edit icon next to the desired project's name.

The Sticky property applies only to the steps in a project that do not specify a selector of their own. If a step has a selector option other than Default, the system uses that selector to choose a server for the step—even if the selector is the same as the project's selector.

When the Sticky property is set, the project uses the same server for every step whose selector field is set to Default.

When the system starts an inline project, the system uses the inline project's selector as the default selector for the steps of the inline. The Sticky property of the calling project does not affect the inline project, and the inline project obeys its own Sticky property if it is set.

When the system starts an inline library, it obeys the following rules:
Note: You can use the .bset server command to change the default server for a project during the job. Steps that occur after the .bset command use the new default set by that command, and stick to that new server.

Feedback