Hot answers tagged

11

If the teamcity start script is a LSB-compliant init script (that is, if it provides start, stop and other arguments), you can just copy the script to /etc/init.d folder and run (as root): # chkconfig --add <script_name> # chkconfig <script_name> on A symbolic link for the file should be OK too. So try (as root): # ln -s ...


10

Having just spend around 4 hours trying to configure SSL for TeamCity (and using the answers in this thread), I managed to get this working using the server farm option. I configured a TeamCity server farm which included my TeamCity server on 127.0.0.1 using port 8080, and allowed the Application Routing Rules to create a corresponding server farm routing ...


5

In case anyone else stumbles on this, Team City has a Deployer plugin which supports moving artifacts to a Samba share, FTP server or SSH server: http://confluence.jetbrains.com/display/TW/Deployer+plugin


5

Using the roles and permissions in Teamcity, you can have a project that only your deployment team has access to. It can have an artifact dependency on the main build, and you can even have it used "last pinned build" so developers can control what's even available. I would install a build agent that is able to deploy to the target system(s), and then use ...


5

in Fedora 17 command # chkconfig --add teamcity-server say: service teamcity-server does not support chkconfig you should add header like: #! /bin/bash # chkconfig: - 10 90 only after that run first command.


3

Under the build configuration setting on "Configuration Step 3" -> "Build Steps" add as first step a "Command Line" step which calls bundle install. Don't forget to set the Ruby environment (as above under "Configuration Step 3" -> "Build Steps") by adding a "Build feature" and selecting "Ruby environment configurator". You can then select your rvm ruby ...


3

With the Amazon EC2 Basic Linux instances the ports 1-1023 are privileged, so when I tried to start teamcity as non-root user it was crashing because I was trying to access a privileged port. I found this out through this stackoverflow question It outlines 2 solutions: start teamcity as root user run teamcity as service with jsvc


3

I don't know if there's something you can do within Tomcat to listen for HTTP host headers, but if you install Apache, have it listen on port 80, and depending on the HTTP host that's requested (virtualdir) have it do a Proxy connection back to the tomcat instance on their respective ports.


2

TeamCity in tar.gz contains Tomcat. YouTrack in .jar edition includes Jetty. We have a short guide on how to setup TeamCity and YouTrack to run on the same server.


2

The easiest option is just to use the copy feature from within the tool (go to Administration and there should be Copy links both at the project and the build level). It will make a reasonable copy of the the configuration and allow you to alter for the specific new project. The configurations are contained in ${HOME}/.BuildServer/config/${config_name}. ...


2

I was able to get help from Jet Brains on this issue and TeamCity needed to be patched to pull in the proper environment variable. More information can be found here: http://youtrack.jetbrains.net/issue/TW-12785


2

For securing the web deploy process, if you are on a domain, you can setup web deploy to accept windows authentication and then have the teamcity build agent run as the domain user who has permission to deploy in IIS. I have things setup this way, and you do not need any kind of passwords in the web deploy script. Setting up windows authentication for web ...


2

#! /bin/bash #First argument ($1) would be the name of the file to be unzipped #Second argument ($2) would be where to unzip the files to (absolute path) unzip $1 -d $2 find $2 -name *.sh -print0 | xargs -0 chmod +x This would work as long as the files you were wanting to make as executable were always going to be *.sh. Otherwise could always add a third ...


2

The quickest and easiest solution would probably be to use a shell script that addresses your permissions after running the unzip.


2

When the script is run manually, it works correctly. But, when run automatically it doesn't work. I've found the culprit: TeamCity runs under the user teamcity. It must be present in the /etc/sudoers file and you should add, using visudo a line like this: Defaults:teamcity !requiretty


2

You don't need to setup a domain/DNS. If you assign Elastic IPs, you can use the Elastic IP Public DNS name, and it will resolve to the external IP if you query it externally, and resolve to the internal address if you query it from other EC2 instances. So if I've got an Elastic IP of 54.254.54.54, the public hostname is ...


2

What I usually do is bake the publishing / copying /deployment (ie- downloading) of things directly into the build script that TeamCity uses instead of setting things up as artifacts. Alternatively, you could set up a new build config that would automatically start after your first build is done. It would take your project's artifacts as dependencies and ...


1

LDAP authentication usually works like this: The LDAP client (which would be the TeamCity server in this case) asks the LDAP server if a certain username/password combination is valid. The LDAP server checks this and answers with yes or no. At no point does it transmit the password back to the client. From my short skimming the docs, I understand TeamCity ...


1

I have just gone through the same process as yourself on Windows Server 2008 R2. I wanted a wildcard certificate to work with Gitblit and other services that I wanted to run. First of all I created the CSR in IIS and installed the certificate into there. I had done this before and was wanting to use the certificate in IIS anyway so this made sense to use ...


1

I solved the problem by going into TeamCity folder\conf\ and opening up server.xml. About halfway down there was the following: <Connector port="80" protocol="HTTP/1.1" connectionTimeout="60000" redirectPort="8543" useBodyEncodingForURI="true" /> So I changed the port attribute to 81 and restarted the ...


1

I had a similar issue with TeamCity. Error: 'git fetch' command failed . . . Caused by Missing commit. Fetching on my development machine worked fine. Also, the missing commit was present using command line. $ git show b18264d I fixed this error by: Cloning a bare repo from my local git repo $ git clone --bare MyGitRepo MyGitRepo.git Replacing the ...


1

If I understand well you should edit ldap-mapping.xml (or create it as a copy from ldap-mapping.xml.dist). You can create a map in this file. <!DOCTYPE mapping SYSTEM "ldap-mapping.dtd"> <mapping> <group-mapping teamcityGroupKey="ALL_USERS_GROUP" ...


1

I resolved this issue after a Java upgrade on our TeamCity instance by setting the jsse.enableSNIExtension property based on a the top answer given to http://stackoverflow.com/questions/7615645/ssl-handshake-alert-unrecognized-name-error-since-upgrade-to-java-1-7-0 The correct way to do so will depend on the version of TC you're running, as documented at ...


1

How about making Chocolatey do this: cinst TeamCityAgent -params 'serverurl=http://servername:8081 agentName=Build1' It seems that you still have to open firewall ports, though. This is from Asger Hallas's comment in the link above: New-NetFirewallRule -DisplayName "Allow TeamCity" -Direction Inbound -Protocol TCP -LocalPort 9090 -Program "c:\program ...


1

I found a file called BUILD_27402 in webapps/ROOT. The file has no contents (0Kb), but 27402 matches the build number for version 8.0 as listed on their previous releases page. So the answer is to look for that BUILD_xxxxx file in webapps/ROOT Thanks, me. :)


1

I know nothing about Teamcity and would defer to Catbird55's answer regarding the server. However, on the Ubuntu side, it's not enough to just copy the id_rsa.pub file to the remote servers. You need to determine the userid that Teamcity will be using to connect to the servers, and then add the contents of id_rsa.pub to the authorized_keys for that user: ...


1

I don't know whether Cloud solution would be acceptable for you but there is a company which is offering Jmeter as a Service - ie basically SaaS solution. They claim that they have rich scripting capabilities so it might be one of the options for you. http://aws.amazon.com/customerapps/3299 http://blazemeter.com/ I never used their services myself though ...


1

The manifest provider is designed to sync multiple providers at one time: msdeploy verb:sync -source:manifest=manifest.xml -dest:auto,computerName=... Then manifest.xml is: <multipleAcls> <setAcl path="path1" setAclAccess="Write" /> <setAcl path="path2" setAclAccess="Read" /> <setAcl path="path3" ...


1

It seems that was a problem with the JAVA heap size or memory options at startup TeamCity. I had to set the following environment variables: export TEAMCITY_SERVER_MEM_OPTS="-Xmx1300m -XX:MaxPermSize=270m" export TEAMCITY_SERVER_OPTS="-Dteamcity.git.fetch.separate.process=false"



Only top voted, non community-wiki answers of a minimum length are eligible