Cruise allows you to model your develop, deploy, test and release process so that everybody has visibility into and control over the process. Cruise's unique and revolutionary deployment pipelines let your team self-service builds into your environments, lock them down so only the people you specify have access to them, and records who performed which deployment.
Pipelines are grid-enabled, so you can split a stage into many jobs which get run simultaneously on your build grid. Split your test suites into multiple jobs, or run them on multiple environments, and have Cruise roll up the results. If your deployments require running tasks on multiple servers, you can do that too.
Cruise's build cloud is zero configuration. Just install Cruise Agent on a computer and tell it the hostname of Cruise Server and it will start picking up jobs and doing work, checking out code if necessary. You can even re-run old jobs or re-deploy old builds -- Cruise Agent will automatically update your sandbox to the correct revision.
Cruise features end-to-end security. It integrates with LDAP and Active Directory to authenticate users, and (new in Cruise 1.1) provides role-based authorization to control who can trigger individual stages within pipelines. You can also control who has administrative access over Cruise Server. Agents communicate with the Server over a secure connection, with Cruise transparently creating a zero-configuration public key infrastructure to lock down all communication. An administrator must manually approve any Agent joining the build cloud.
Pipelines are grid-enabled, so you can split a stage into many jobs which get run simultaneously on your build grid. Split your test suites into multiple jobs, or run them on multiple environments, and have Cruise roll up the results. If your deployments require running tasks on multiple servers, you can do that too.
Cruise's build cloud is zero configuration. Just install Cruise Agent on a computer and tell it the hostname of Cruise Server and it will start picking up jobs and doing work, checking out code if necessary. You can even re-run old jobs or re-deploy old builds -- Cruise Agent will automatically update your sandbox to the correct revision.
Cruise features end-to-end security. It integrates with LDAP and Active Directory to authenticate users, and (new in Cruise 1.1) provides role-based authorization to control who can trigger individual stages within pipelines. You can also control who has administrative access over Cruise Server. Agents communicate with the Server over a secure connection, with Cruise transparently creating a zero-configuration public key infrastructure to lock down all communication. An administrator must manually approve any Agent joining the build cloud.
