Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • The server checks all the actions in current stage and picks the next available agent that can run all the actions.
  • The server sends all the required information to the agent including repositories, variables, files and actions.
  • The agent then steps through and executes each action in the stage.
  • The agent sends all the designated information back to the server.
  • The server moves onto the next stage and begins the workflow again.


Figure 1. Continua's server and agent architecture


Single Build over Multiple Agents


  • Workspace files: Workspace files are any files that are used in the Build Workspace. Build workspaces are where builds are executed and generally this is where you put files that the build needs to execute actions. For example, this is where agents temporarily store source code while a project is being built. The build workspace should also be used as the output location for any compiled projects. Workspace Rules define which files should be transferred between the agent and server build workspaces. These rules can be defined on the stages page in the Configuration Wizard. By default, the Workspace rules are setup so they will only transfer files that are in the Build Workspace's Output subdirectory. This folder can be accessed with Expressions by using the following syntax: $Workspace$\Output.
  • Repository files: These are files that are pulled from your source repositories and copied into your Build Workspace. Any Source repository files that are required for a particular stage must be transferred to the Build Workspace via Repository Rules. Repository rules are defined per stage and can be set on the stages page in the Configuration Wizard. By default, all files from your source repositories are copied into your build.
  • Artifact files: These are the files that you want to register as artifacts of the build. Artifact files can be viewed and downloaded directly through the Continua CI interface. Artifact files must be transferred from the agent to the server using Workspace Rules, then they can be registered as artifacts. All artifacts are registered using Artifact Rules which are set on the stages page in the Configuration Wizard. By default, no files are registered as artifacts.