In case when you reset (Administration -> Diagnostics -> Caches -> versionedSettings) or somehow currupt cache of versioned setting — teamcity can fail of applying new versions of settings from repository.
In this case login to TeamCity server host. Navigate to <teamcity_data_dir>\system\caches\versionedSettings\ dir. And find which subdirectry contains settings of you project. Copy files fom .teamcity\ folder of you project repository to this dir to fix the issue
In this case login to TeamCity server host. Navigate to <teamcity_data_dir>\system\caches\versionedSettings\ dir. And find which subdirectry contains settings of you project. Copy files fom .teamcity\ folder of you project repository to this dir to fix the issue
in case when vcs trigger doesn`t work when you configure TeamCity with Kotlin — try to add appropriate import
import jetbrains.buildServer.configs.kotlin.v10.triggers.vcs
triggers {
vcs {
}
}
You can import projects with all their data and user accounts from a backup file to an existing TeamCity server
(note that the major and minor versions of the source and target TeamCity servers have to be the same)
confluence.jetbrains.com
How to strip color codes out of stdout
unix.stackexchange.com
can be useful when you show test reports in TeamCity
unix.stackexchange.com
can be useful when you show test reports in TeamCity
youtrack.jetbrains.com
There are couple issues with push agent functionality:
— by default wrapper.ntservice.interactive setting in the buildAgent/launcher/conf/wrapper.conf configuration file is set to true — this brings to error during agent installation with psexec:
in the push agent logs:
in the windows event logs on agent host:
— it would be good to determine if push agent functionality used to install agent on EC2 host and set wrapper.ntservice.dependency.1=Ec2Config setting of the buildAgent/launcher/conf/wrapper.conf configuration file. As mentioned in manual (https://confluence.jetbrains.com/display/TCD9/Setting+up+and+Running+Additional+Build+Agents#SettingupandRunningAdditionalBuildAgents-BuildAgentasaWindowsService). Or provide corresponding configuration option in the Agent Push preset configuration dialog
— to simplify agent push configuration on the AWS please add note to manual about 445 port that should be configured in the AWS::EC2::SecurityGroup attached to build agent host. This allow to communicate psexec from TeamCity server host with build agent host
There are couple issues with push agent functionality:
— by default wrapper.ntservice.interactive setting in the buildAgent/launcher/conf/wrapper.conf configuration file is set to true — this brings to error during agent installation with psexec:
in the push agent logs:
bootstrapper.exe exited on MY_AGENT_HOST_IP with error code 255.
Remote agent installation failed: Command 'D:\:\teamcity\temp___5060497447753492559\cli-wrapper.exe D:\teamcity_data\system\pluginData\psexec\psexec.exe /accepteula \\MY_AGENT_HOST_IP -e -h -u MY_USER -p ********** -c -f D:\teamcity\temp___5612841585882618839\bootstrapper.exe bootstrap -u MY_TC_MASTER_HOST – bin\install.bat MY_TC_MASTER_HOST C:\\BuildAgent 27f25fcd78b2812602f9a14ea6756bae' was executed with error message(s): Execution error. Return code=255
in the windows event logs on agent host:
The TeamCity Build Agent service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.
— it would be good to determine if push agent functionality used to install agent on EC2 host and set wrapper.ntservice.dependency.1=Ec2Config setting of the buildAgent/launcher/conf/wrapper.conf configuration file. As mentioned in manual (https://confluence.jetbrains.com/display/TCD9/Setting+up+and+Running+Additional+Build+Agents#SettingupandRunningAdditionalBuildAgents-BuildAgentasaWindowsService). Or provide corresponding configuration option in the Agent Push preset configuration dialog
— to simplify agent push configuration on the AWS please add note to manual about 445 port that should be configured in the AWS::EC2::SecurityGroup attached to build agent host. This allow to communicate psexec from TeamCity server host with build agent host
А вот что мешает прикрутить к teamcity автоматическую накатку новых версий? Как это например в эклипсе сделано? Религия не позволяет ?
Build configuration was paused by vshapranov a few moments ago with comment: Every time you use qmake from necessitas, God kills a kitten. [Activate]
А оно ни у кого не ест память под маком? Safari с открытой страницей My Changes скушал 1.6 ГБ за 2 часа :) Firefox не использую, но в рамках теста он уже скушал 100 метров за полчаса :) с той же одной открытой страницей.
При билде на CI сервере рекомендуется сначала сделать mvn clean. Но это лишь частично верно. Лучше всего делать clean не мавеном, а просто удалять всю checkout directory. Особых проблем с VCS не вызовет — в том же TeamCity есть кеш — то есть checkout каждый раз не значит, что будет нагрузка на vcs — все будет из кеша взято. Чем это лучше? Тем, что clean работает на основе того реактора, что и все остальные заклинания — в случае какой-либо ошибки в POMs, target некого модуля может остаться (предположим, у вас есть кастомный плагин, который резолвит артефакты не по координатам, а просто по физическому пути) и вы в результате получите удачный билд с устаревшими артефактами.