Teamcity clearcase setup

Enable this option to use this VCS root in other projects or build configurations. See also:. You are viewing documentation of TeamCity 7. Please refer to the listing to choose another version. Icon If you plan to use agent-side checkout mode , make sure ClearCase client cleartool is also installed on agents and properly configured, i. Icon Do not use the view you are currently working with. Icon Some public servers can block access if polled frequently.

Powered by Atlassian Confluence 5. Report a bug Atlassian News Atlassian. Search Search Table of Contents. Common VCS Root properties are described here. The section below contains description of the fields and options specific to the ClearCase Version Control System. ClearCase view path. A local path on the TeamCity server machine to the ClearCase view created during the initial setup.

The snapshot view is preferred as there is no benefit in using the dynamic view with TeamCity. Also, dynamic views are not supported for the agent-side checkout TW Do not use the view you are currently working with. TeamCity calls the update procedure before checking for changes and building patch, and thus it might lead to problems with checking in changes.

Relative path within the view. Branches are used in the "-branch" parameter for the "lshistory" command to significantly improve its performance. If you're using Tomcat J2EE container, make sure Apache Portable Runtime feature of this container is disabled actually it is disabled by default. Unfortunately because of bugs in Apache Portable Runtime , TeamCity may not work properly in this case.

If you want to use another version of Tomcat web server instead of the bundled one, you have the choices of whether to use the. For the latter, you might want to:. Upon successful installation, the TeamCity server web UI can be accessed via a web browser. The default address that can be used to access TeamCity from the same machine depends on the installation package and installation options. Port 80 is used for Windows installation, unless another port is specified, port for.

One of the most common issues with the server installation is using a port that is already used by another program. If you use the TeamCity server Windows installer, you can set the port to be used during installation. If you use the. Use the following instructions to change the port if you use the.

If another application uses the same port as the TeamCity server, the TeamCity server Tomcat server won't start and this will be identified by "Address already in use" errors in the server logs or server console. TeamCity both server and agent requires JRE 1. It is recommended to use 32 bit installation unless you need to dedicate more memory to TeamCity server.

Please check 64 bit Java notes before upgrade. Note that on upgrade, TeamCity will overwrite the existing JRE with the bundled bit version, so you'll have to update to the bit JRE again after upgrade.

TeamCity server can run under both the and bit JVM. It is recommended to use the bit JVM unless you need to dedicate more than 1.

To change the memory settings, refer to Configuring TeamCity Server Startup Properties , or to the documentation of your application server, if you run TeamCity using the. The recommended approach is to start with initial settings and monitor for the percentage of used memory see also TW at the Administration Diagnostics page. The default placement of the TeamCity data directory can be changed. See corresponding section: TeamCity data directory for details. After successful server start, any TeamCity page request will redirect to prompt for the server administrator username and password.