teamcity

问题 The same deployment works correctly on windows, and on linux - but using teamcity and its built in maven I get an error. Local deploys, and the error is : the container configuration directory "/BuildAgent/work/68d4a71c8dc5cfd9/target/cargo/configurations/tomcat8x" does not exist. Please configure the container before attempting to perform any local deployment. The relevant section of pom looks like this : <plugin> <groupId>org.codehaus.cargo</groupId> <artifactId>cargo-maven2-plugin<

问题 I am trying to deploy Visual Studio 2012 SSDT project to Sql Server using TeamCity 8 and MSBuild Publish task but the deployment fails. When I look at TeamCity logs and use /v:diag switch in my build configuration I see that for unknown reason MSBuild searches for MyProject .sqlproj .publish.sql and for MyProject .sqlproj .dacpac files. The exact error: [SqlPublishTask] C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets(1233, 5): File

问题 I am using TeamCity Professional 8.1 and YouTrack 5.0.6. I have managed to fill "Fixed in build" field in YouTrack with two step workflow. I am using #issue-id Fixed command in my Merucrial commit message to change the state of issue in YouTrack. I made some changes in code ( not related to fixed issue) and I push changes to the server. When TeamCity finishes the build with changes from the second step it fills the "Fixed in build" field of my issue with the build number. But the issue was

问题 I have JIRA and TeamCity running on two separate servers both accessible via HTTPS and self signed certificates. I would now like to integrate JIRA as TeamCity's issue tracker. However, when I try and setup the connection from TeamCity I get a CertificateException . TeamCity is on a Ubuntu 101.10 machine and I tried to import the certificate from the JIRA server into /usr/lib/jvm/java-6-openjdk/jre/lib/security/ but this made no difference. 回答1: The command for importing a self-signed

问题 I need to create zip archive artifact which contains two folders. I know how to create one folder archive: Folder1 => myartifact.zip But how can I tell TeamCity to add Folder2 to same archive? 回答1: The same target_archive name can be used multiple times, for example: */.html => report.zip */.css => report.zip!/css/ See also: http://confluence.jetbrains.net/display/TCD7/Configuring+General+Settings#ConfiguringGeneralSettings-artifactPaths 来源： https://stackoverflow.com/questions/10953063

问题 Does anyone know of an easy way to show the build version number in an HTML/JavaScript project that uses AMD? The version number is generated by TeamCity as part of the build process. Here is what I mean in more details: One of my js files (e.g. showVersion.js) has a line like this: alert('Build version: __build_ver_placeholder__ '); Ideally, after TeamCity completes the build, it will plug in the actual version number for the place-holder. And the line above will become: alert('Build version

问题 I have a parameter for which I'm showing a prompt. I've set a default value for it and that works fine. What doesn't work, however, is that if I choose to enter a different value when running the build, then on the next build this value automatically becomes the new default value, so to say. I'd like the default value to always be fixed and if you enter a different value in the field, then that value will be used just for this build (and the next build will fallback to the fixed, default

问题 I have a TeamCity build step which runs a PowerShell (.ps1) script, which looks like this: try { # Break something $a = 1 / 0 } catch { Exit 1 } Despite this, in the build log, the step succeeds and exits with code 0. [10:02:18][Step 2/3] Process exited with code 0 I want the step to fail if there are any failures in the script. How can I make this happen? We are using TeamCity Enterprise 8.0.5. 回答1: I have just discovered this post: PowerShell runner - script fails but the build succeeds -

问题 There is a known problem that if you deploy during a TeamCity build, a previous version will be deployed (as the current will be available only after the build is finished). Documentation suggests creating a secondary TeamCity BuildConfiguration as a workaround but it sucks and seems not to work anymore (there is a number of bug reports about it). There was an alternative solution suggested in the comments to this question. The idea is to push your current build nuget package to the Octopus

问题 I have a single project with three build configurations: Integration Deploy Dev Deploy Release Build configs 2 and 3 are dependent on 1 via a snapshot. There are 3 VCS roots: Git - All (used with build config 1) Git - Develop (used with build config 2) Git - Master (used with build config 3) The default branch and branch specs are as follows: Git - All default branch: develop branch spec: +:refs/heads/(develop) +:refs/heads/(master) +:refs/heads/(feature/ ) +:refs/heads/(hotfix/ ) +:refs