1

I'm having a .net WPF project that compiles to a bunch of dlls. I also have another project that compiles all the dlls and creates an installator exe.

I am also using TeamCity to automatically do those tasks for me with a press of a button.

The problem is that I want to have a separate TeamCity build configuration intended to automatically copy the result installator exe to a number of remote machines, each having specific credentials. But, unfortunately, I don't get how do I do this.

I have found some articles on automatic deploying (like this http://www.troyhunt.com/2010/11/you-deploying-it-wrong-teamcity.html), but, obviously, they are very specific for web projects.

So, how should I correctly deploy my installator on build?

Maksym
  • 458
  • 4
  • 23
  • Do you consider a "deploy" to be a full installation of the executable? Or are you just looking to copy the installer from the build machine to some other machine(s)? – Bryan Ray Nov 28 '12 at 15:57
  • @Bryan Ray, I mean just plain copying the installer file. – Maksym Nov 28 '12 at 19:48

2 Answers2

0

Your best bet is to research NAnt and make a simple task that will copy the TeamCity artifact (installer) out to the specified location.

All you would need to do is have TeamCity execute the specified NAnt task after the installer has been built.

http://nant.sourceforge.net/release/0.85/help/tasks/copy.html

Update

Also, check out this question for solutions on specifying the credentials for the copy task.

Community
  • 1
  • 1
Bryan Ray
  • 931
  • 10
  • 26
  • But how do I specify the credentials to copy the artifact to a remote server? I don't see any properties for that in the copy task. – Maksym Nov 29 '12 at 09:25
0

OK, I've found out that it's pretty easy to do this using the FtpUpload MSBuild community task. There, one can set up the credentials and all other stuff needed for uploading a file (or a set of files) via ftp.

Maksym
  • 458
  • 4
  • 23