Tag Info

Hot answers tagged

9

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 ...


8

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 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.


4

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 ...


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.


3

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


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

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 quickest and easiest solution would probably be to use a shell script that addresses your permissions after running the unzip.


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

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 ...


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"


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

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

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


1

You should create the archive with a Unix zip to preserve the Unix attributes.


1

Seems you do not need any rewrite rules. Check TeamCity server context path is the same as in your public server, i.e. http://public.com/contextPath and http://localhost:8080/contextPath. TeamCity uses request URI to generate NuGet feed, so you should make sure your proxy provides HOST, X-Forwarded-Host, X-Forwarded-Server, X-Forwarded-For headers. You may ...


1

Ah, the power of posting. After asking the question, I decided to take a look at the rules I had setup one more time. The rules were setup on the site level. I moved them to the server level, and everything works like a charm.


1

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 ...


1

Check user account that you use to run TeamCity windows service. Also check if Team Explorer is able to connect to TFS from the user account you use to run TeamCity server.


1

It's probably already in use by some other process. You should run netstat -anc | grep 80 as root to find out what process has a LISTEN socket on that port.


1

If your TeamCity server is Internet facing all you need to do is make sure that you have a DNS entry for teamcity.mydomain.com that resolves to the public IP address of your server. If your TeamCity server is behind a gateway device (firewall, router, etc) you'll still need to create the aforementioned DNS entry, but you'll want it to resolve to the public ...


1

As a first step I would recommend saving your long command line into a batch file (e.g. LaunchWI.cmd) and calling this batch file from the TeamCity build agent. When you launch an app from a windows service the current working directory will be set to c:\windows\system32 - this can potentially cause some issues. Try adding C: CD "\Program ...


1

You could also use a connector to do so. There is the old ISAPI connector (redirector) available from Apache directly or there is also a new one available from RiaForge (this one seems easier to get running). http://tomcatiis.riaforge.org/


1

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

Jetbrains try this out it will take you 2 hour setup every thinks



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