teamcity

问题 I have a project in teamcity that has the following structure. The developers develop against some git repository. They push their changes and the teamcity CI build does its job. I would like to chain a Release build to it to publish changes to a Github repository once everyone agrees. I understand how I could do this through a command line script but I was wondering if I could declare a VCC (that won't be used for pulling) and somehow push to it? Otherwise I have unencrypted passwords on my

问题 In TeamCity, I would like to have one build configuration that picks up all branches in our SVN without having to manually specify them out. Is it possible do this? I've tried configuring the checkout rules with the following wildcard +:branches/* but the system seems to reject the wildcard being there or doesn't know what to do with it. Is it possible to checkout a HEAD revision in SVN irrespective of branch/tag/trunk? 回答1: You don't need checkout rules for that, just specify top-level URL

问题 I use jmeter-maven-plugin (version 1.10.0) to run JMeter test - first I run it from IntelliJ, then from TeamCity (for both - command: mvn jmeter-graph:create-graph ) When I want to use the following configuration for jmeter-graph-maven-plugin : <plugin> <groupId>de.codecentric</groupId> <artifactId>jmeter-graph-maven-plugin</artifactId> <version>0.1.0</version> <configuration> <inputFile>${project.build.directory}/jmeter/results/*.jtl</inputFile> <graphs> <graph> <pluginType

问题 In my teamcity it is working fine When I use the VCS checkout mode from the server But when I use the build agent it is not working when I run a build it says (failed in applying the patch and it says Cannot connect to the X server) . My build agent is a Linux machine . Here I run my build agent . I configured build agent for generating the War files which is working fine . But I choose to VCS check out mode at the teamcity Version Control settings and run the build I am getting this error

问题 I am trying to create the release steps for SSDT project in VSTS but the build artifacts are available in TeamCity. For that I installed TeamCity artifacts for Release Management extension in VSTS. After installed above extension in VSTS, then I am trying to link the build artifacts to release configuration. so, I tried to configure the TeamCity endpoint and verifying the connection to the TeamCity. Then I got the error like below screenshot. Next I tried to add the build artifacts in VSTS

问题 How do I label my SVN project with TeamCity VCS labeling if I am using a checkout rule? I read the checkout rule docs, but I'm having a hard time understanding the relationship between VCS labeling and checkout rules in TeamCity. My SVN structure looks like: https://my.internalsvn.com/(...)/myproject/branches/gattaca-dev https://my.internalsvn.com/(...)/myproject/tags https://my.internalsvn.com/(...)/myproject/trunk In TeamCity, my VCS root is configured to: https://my.internalsvn.com/(...)

问题 I'm trying to connect my TeamCity project to my TFS project with a free account (a windows live account). But I'm having a little bit a trouble doing this. I'm getting the error TF30063 (You are not authorized to access /DefaultCollection/). I've tried a lot of things, I even follow the instruction of this question -http://youtrack.jetbrains.com/issue/TW-20909-, but no luck... I already have: - Set admin permission to all members to my TFS project - Put the project on my computer in a public

问题 I have setup the trigger to listen to the last pinned build artifacts: <TEAMCITY URL>/repository/downloadAll/bt79/.lastPinned However, the trigger keeps firing every 30 seconds which is the default Polling interval. Am I missing something here? The url always gives me the same file. UPDATE: After upgrading to TeamCity 7.1 the problem still exists. 回答1: The answer to this question came from TeamCity support: The reason of the described behaviour is the way TeamCity controller returns data

问题 Background I have a third-party web service with methods for installing and uninstalling an artifact. Both when installing and uninstalling, you specify an artifact named package-%maven.project.version%.zip. Before installing a new package, I need to uninstall the previously installed package. Solutions I found this solution, but as this is the final step to achieve continuous deployment, I need something automated and not a prompt. Another solution that can be automated by a build step is to

问题 I'm creating a Visual Studio Package (vsix) (shameless plug: pMixins ) and I want to build the vsix package using the TeamCity continuous integration server. TeamCity uses MSBuild in the background. I am comfortable installing the Visual Studio SDK on my build agent, but I do not want to install a full version of Visual Studio. When I run the Visual Studio SDK installer, it complains that Visual Studio isn't present. How can I use MSBuild (via TeamCity) to build my vsix without having to