...
Using the editor
Editing Stage Options
Stage Options are defined per stage and offer a number of ways to control the flow of the workflow. When a stage is executed on an agent, the agent will look for any repositories attached to the configuration and copy the contents of those repositories to its local machine. If your stage does not require access to anything in those repositories then there's no use copying those repositories so you would un-ticked the option "Stage requires access to source code". If you would like to stop a build at a certain stage so you can review the result before the next stage executes then you would un-tick the "Automatically promote to the next stage" option.
Note: If a stage is setup to not automatically promote to the next stage, you can later manually promote that stage from the builds page for that build.
Finally, you can choose to put Agent Requirements on the Stage which are checked before the stage is executed. By using conditions you can tell Continua to only executed that stage when all those conditions are met. For example, you can specify that the stage only run on an agent with a hostname of "buildrunner". The condition would look like this:
...
See: Stage Options
Editing Stage Gates
Stage Gates are attached to the previous stage and are simply a list of conditions that must be met before the next stage is executed. For example, you can creat a condition where it will only evaluate to true once the server's local time reaches midnight. Stage Gates also come with default conditions which specify that all unit tests that ran in the previous stage must have passed. You can however choose to remove these default conditions.