The settings include VCS roots, build steps, and build triggers described below.Ī collection of version control settings (paths to sources, username, password, checkout mode, and other settings) that defines how TeamCity communicates with a version control system (VCS) to monitor changes and get sources for a build.Ī task to be executed. ![]() A project is a collection of build configurations.Ī combination of settings defining a build procedure. ![]() All information on the build results (build history and all the build-associated data except for artifacts and build logs), VCS changes, agents, build queue, user accounts, user permissions, and so on, are stored in a database.Ī TeamCity project corresponds to a software project or a specific version/release of a software project. The server itself does not run either builds or tests: the server's job is to monitor all the connected build agents, distribute queued builds to the agents based on compatibility requirements, and report the results. It is possible for the server and an agent to coexist on the same computer, but for production purposes, we recommend installing them on different machines for a number of reasons, the server performance being the most important. Different types of tests can be run on different platforms simultaneously, so the developers get faster feedback and more reliable testing results. Build agents in TeamCity can have different platforms, operating systems, and preconfigured environments. The agent can be installed on a separate machine (physical or virtual, and it can run the same operating system (OS) as the server or a different OS. It is installed and configured separately from the TeamCity server. A piece of software that actually executes the build process.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |