In TeamCity 8.1 we addressed this problem. If a build configuration is inherited from a template, the template settings play the role of the defaults thus, all settings redefined in a build configuration can be easily located.Įasier settings override in inherited build configurationsįor a build configuration inherited from a Build Configuration Template, the settings like the maximum number of running builds, execution timeout, build failure conditions and some others could not be overridden even with the help of parameter references. The settings of a build configuration whose values have been changed from defaults are now marked with an orange border. All complicated options and the settings used not so often are now marked as advanced and are hidden by default (unless their values were changed, in which case the modified advanced settings are automatically shown). To address this problem, we introduced advanced settings. As usual, most of them are useful in a minority of cases, but they often distract new users and make the product look more complicated than it actually is. TeamCity has a lot of options and configuration tweaks. If there are some configuration changes that could improve your build configuration setup, TeamCity will suggest them via a new suggested settings icon: Similarly to creating a project from URL, you can also create a VCS root from a repository URL only:īesides that, if while creating a new VCS root TeamCity detects a duplicated VCS root, it will show a warning and suggest using the existing VCS root: TeamCity auto-detection mechanism supports most popular version control systems and a wide range of build tools and technologies, including: Maven, Gradle, Ant, NAnt, MSBuild, Visual Studio solution, Powershell, Xcode, Rake, IntelliJ IDEA, as well as various command line scripts. It was easy to create a new project before, but now it's really a no-brainer. TeamCity will detect the type of your version control system, create a VCS root for you in the new project, verify connection to the repository, create a Build Configuration, and propose pre-configured Configuring Build Steps to run your build. If you have a URL to a project in a version control system, you can easily create a project in TeamCity using this URL only. Starting with TeamCity 8.0 each Build Agent license adds 10 more build configurations to Professional edition (as well as one agent)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |