Overview

Each project on your pulse™ server is used to build a single code line. The project's SCM configuration is used to define the location of the code line in your SCM server. This location is used for monitoring of the SCM for code changes, determining changes between builds, and checking out the project's source code during a build.

Supported SCMs

pulse™ currently supports the following SCMs:

SCM	Description
CVS	Concurrent Versions System (CVS) is a popular open source SCM.
Perforce	Perforce is a commercial, multi-platform SCM made by Perforce Software.
Subversion	Subversion is an open source SCM designed as a compelling replacement for CVS.

Support for more SCM systems will be added in future versions of pulse™, in line with customer demand.

Configuring SCMs

SCM details for a project are initially configured during the add project wizard. This configuration may be changed at a later time at the "configuration" tab for the appropriate project. Note that significant changes to the SCM details for a project may disrupt features such as detection of changes. If you do make a major change to the SCM details for a code line (e.g. by switching to a new SCM), it is probably best to configure a new project rather than reuse the same project.

Change Viewers

If you already have a third-party web application for viewing your SCM repository, e.g. Fisheye, you can configure pulse™ to link to the external server using Project Change Viewers.

Filtering SCMs

The SCM Filters allows you to filter out modifications that are used to trigger a build. If for example, you have certain files (such as web pages or document files) under source control that you don't want to have trigger the build, you can use an Scm Filter to ensure that their changes will not trigger a new build. SCM filters can be configured via a projects "configuration" tab.