Software relatedAnything related to software goes in here. Ask for help, post info.
Welcome to the VipraSys forums.
You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features such as download links. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, Register Now by clicking here!
Quote:
TeamCity is a distributed build management and continuous integration system that allows your team to run and monitor your software building process while improving team communication, productivity and the integration of changes.
With TeamCity:
* the process of integrating changes becomes a core part of your daily activities,
* integration problems are discovered even before the build is complete,
* you are notified only about the events you are interested in,
* the process of creating builds is quick and transparent.
TeamCity's basic unit of work is a software build. To build your software using TeamCity, you need to have at least one "Build Agent" - a build computer with a set of predefined parameters (such as system and environment variables, JDK version, etc). The build agents are arranged into a build grid. Each software build, in turn, has its own configuration - a set of actions and parameters specified for it. These include the build runner, build schedule, etc. The build agent must meet the builds configuration's requirements: if there is a free build agent that meets the build configuration requirements, the build is started. Otherwise, the build is put into the queue and is processed when a compatible build agent becomes free.
Have a "10,000-foot look" at TeamCity, and the IDE's, frameworks, version control systems and means of monitoring it supports. [Only registered users can see links. ]