Versions Compared

Key

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

...

Consider only branches which meet a specific pattern (using the supplied regex).

Tags

For Tag Aware Repositories (Git, Mercurial and Subversion), the Tags tab sets how Continua handles changeset tags.

Image Added

Tag changes

The options here include: 'Ignore', 'Detect', 'Detect and list as new Changeset'

Detect and list as new changeset (the Default for tag aware repositories)

Detect all tags for the given repository and treat them as a new changeset.

Image Added

Ignore Tags

Do not consider Tags as changes.

Image Added

Detect Branches

Detect tags and show tags next to changeset.

Image Added

Commit / Push Username

The username to use when committing, or pushing for Git, tags to the repository (tags are committed via a Build Event Handler)

Commit / Push Password

The password to use when committing, or pushing for Git, tags to the repository (tags are committed via a Build Event Handler)

Push Repository URL (Git repositories)

The URL for pushing tags to the remote Git repository. If this is left blank the Repository URL will be used.

Tags Path (Subversion repositories)

The path the root directory for your tags

Exclude Patterns

Exclude patterns allow you to ignore incoming changesets for a repository based on the files that were changed. Changesets will be ignored if every updated file in the changeset matches your exclude patterns. For example, you could set your exclude patterns up so that if any old files (files that end in .old) were changed then Continua will ignore that changeset. Note that if another file was also modified in that changeset that does not match the exclude pattern, then the changeset will still be added to Continua.

...