teamdeploy Forum Rss Feed

New Post: Parameterizing Product Code, Product Name and Path

bquarterman — Thu, 17 May 2012 23:18:38 GMT

The documentation at http://teamdeploy.codeplex.com/documentation states:

"UninstallName" (use either UninstallProductCode or UninstallProduceCode)"

Should this instead say:

"UninstallName" (use either UninstallProductCode or UninstallName)" ?

If so, being able specify just the Product Name in the case where a new Product Code is generated for the MSI for every build (i.e. Major Upgrade) is useful. However, a further challenge is when the Product Name also changes between releases (e.g. it includes the version number as a suffix).

If not, apart from updating the Deployment Script from Team Build for every release, has anyone used any other approach?

It would be great if there was an option to set all of the parameters straight from Team Build rather than in the Deployment Script as then you could simply pass any values in (e.g. path of MSI, Product Code, Product Name etc). If you wanted to perform multiple installs, you'd have multiple Deploy Activity and corresponding parameters, one set for each environment.

New Post: How can I see the RemoteExecute output detail

karenwoo — Fri, 24 Feb 2012 01:25:50 GMT

When it failed, only output exit code 1. I want to see the detail , how can I do this? Thanks~

New Post: Location of MSI Deployment?

MichaelDBang — Tue, 30 Aug 2011 22:58:20 GMT

Setting the "TargetPlatform" property in the installer Deployment Project Properties to x64 seems to place the keys in the expected location.

New Post: Location of MSI Deployment?

MichaelDBang — Tue, 30 Aug 2011 16:54:56 GMT

Ah... I think I found the problem. The uninstall/install code doesn't account for 64-bit (Wow6432Node) installations.

My installation is found at the following path in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{UninstallCode}

New Post: Location of MSI Deployment?

MichaelDBang — Tue, 30 Aug 2011 16:24:31 GMT

Hello,

I am currently trying to deploy to a remote machine, and it is saying that the MSI is "deployed" or "installed." However, when I go into Programs and Features ==> Uninstall a Program, my MSI is nowhere to be found. Any idea on where it might be? :)

Thank you,

Michael

New Post: Does this copy anything?

mikedouglas — Wed, 03 Aug 2011 02:25:09 GMT

Hi Vaccano,

The Deploy task installs a MSI to one to many target machines. It runs it from any UNC. When a MSI is run from a remote location, it will copy itself to a local temp folder before it runs on each machine. The other features of it supports uninstalling, stopping/starting services, and passing additional arguments to the MSI. Take a look at the example XML in the document tab. to see the implementation.

Thanks,
Mike

New Post: Does this copy anything?

vaccano — Mon, 01 Aug 2011 15:05:50 GMT

I am trying to get the "Deploy" task into my build script.

I am wondering if the Deploy task actually copies the MSI to the destination somehow, or if it just handles the killing and running of the app?

New Post: Where do the PsTools Go?

vaccano — Fri, 29 Jul 2011 19:32:25 GMT

Thank you the answer!

New Post: Where do the PsTools Go?

mikedouglas — Thu, 28 Jul 2011 21:51:36 GMT

Hi,

I typically manually deploy the pstools to c:\pstools folder on each build server. However, with the dynamic nature of Team Build 2010, I think that is a good idea to check the files into source control and referece the SourceDirectory variable to pass in the to the Team Deploy activities. Keep in mind if you are using a shared team project for your custom build activities path, you would need to include that in your workspace for the build.

Thanks,

Mike

New Post: Where do the PsTools Go?

vaccano — Thu, 28 Jul 2011 20:19:40 GMT

I downloaded the PsTools, but where do I put them? They just come as a Zip file (not an msi or anything).

I doubt that the build tasks are looking in the downloads folder for a folder called PsTools....

So where should I put them? Should I check them into source control with the custom activities?

New Post: Deploy Script Documentation

mikedouglas — Sat, 05 Mar 2011 05:55:18 GMT

Hi guys,

I just uploaded the some documentation of the activities, properties, and xml details. There is also an example of the XML at the end. Please let me know if you want to see any additional information? For a sample of calling RemoteExecute, you can do this. I recently added the OverridePSExecArgs to specify any PSExec arguments desired.

I hope this helps,

Mike

New Post: Deploy Script Documentation

AndrewBA — Fri, 04 Mar 2011 09:30:24 GMT

Hi Gary,

I never succeeded in using the XML build configurations but ended up using Team Deploy's RemoteExecute to fire a powershell script on the deployment machines which performs my deployment process.

If you download the source for Team Deploy you'll find how it uses PsExec so if you familiarise yourself with PsExec's options then you should be able to make it do what you want. I certainly ended up altering the PsExec command line options used.

You may also want to look into PowerShell Remoting or TFS Deployer for other ways to achieve the same thing, but this is working for me.

Andrew

New Post: Deploy Script Documentation

GaryR — Fri, 04 Mar 2011 05:00:00 GMT

Have you had any luck with this yet I am trying to the exact same thing... if you have anything or examples I would appreciate them.

Gary

New Post: Deploy Script Documentation

AndrewBA — Thu, 10 Feb 2011 16:52:01 GMT

Hi.

I'm looking for some documentation on what can be placed inside an XML build script. I'm installing Team Deploy on TFS2010 and am struggling to configure the deploy process for our environment.

We don't use MSIs for deployment at present, but I want to use the RemoteExecute action to run scripts on the target machine.

Thanks in advance

Andrew

New Post: Deployment project from TFS Client

theron — Wed, 09 Feb 2011 21:31:37 GMT

I am doing builds on a TFS client machine. I can build the msi on this machine, but the automated builds are on the TFS server and this is not a TFS server. I do not have access to install either Team Deploy or pstools on the TFS Server. I believe this means this solution will not work for me, but if anyone can confirm this, I would appreciate it.

Thanks

New Post: MSIPathFile

timstspry — Sun, 06 Feb 2011 04:25:29 GMT

Thanks again Mike. Yes, copying the msi's to a temp folder and then having a static temp folder will work. I do like the idea you have of having a property to tokenize the MSIPath.

Thanks again for all of your efforts!

Tim

From: [email removed]
To: [email removed]
Date: Sat, 5 Feb 2011 20:11:59 -0800
Subject: Re: MSIPathFile [teamdeploy:244807]

From: mikedouglas

Tim,
One way I have handled this for other projects is that I copy the MSI from the build definition folder to a temp location. Then the deploy script can be a static temp folder. I still think it would be good to have some sort of variable capability in the script. I was thinking of having a property on the deploy task called: DeployVariables and then it will essentially do a search and replace in the script for any variable names with something like %'s around it. So you could have %MSIPath% in the deploy script MSI. Passing it in the Deploy task as DeployVariables="MSIPath: \\buildservername\Build_Staging\Main - Release_20110205.1".
Let me know what you think.
Thanks,
Mike

Read the full discussion online.
To add a post to this discussion, reply to this email (teamdeploy@discussions.codeplex.com)
To start a new discussion for this project, email teamdeploy@discussions.codeplex.com
You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.
Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com

New Post: MSIPathFile

mikedouglas — Sun, 06 Feb 2011 04:11:56 GMT

Tim,

One way I have handled this for other projects is that I copy the MSI from the build definition folder to a temp location. Then the deploy script can be a static temp folder. I still think it would be good to have some sort of variable capability in the script. I was thinking of having a property on the deploy task called: DeployVariables and then it will essentially do a search and replace in the script for any variable names with something like %'s around it. So you could have %MSIPath% in the deploy script MSI. Passing it in the Deploy task as DeployVariables="MSIPath: \\buildservername\Build_Staging\Main - Release_20110205.1".

Let me know what you think.

Thanks,
Mike

New Post: MSIPathFile

timstspry — Sat, 05 Feb 2011 22:59:25 GMT

Hello, I have need to pass in a variable which would be the path to the MSI's that I want to deploy. All the examples that I have seen so far are referencing a static share which works well. But, from a build and deploy perspective you would ideally want the path to the msi's to be deployed to map to the output directory of any given build which will change from build to build. For example, if I had a build definition named Main - Release and my build numbering schema was yyyymmdd.buildnumber the the first build for Saturday, February 5th 2011 would result in a directory being created on the build server share of \\buildservername\Build_Staging\Main - Release_20110205.1 which is where the .msi's would reside that I would want to deploy. So, I would need to pass in this value as the <MSIPathFile> to Team Deploy.

Any help would be appreciated!

Tim

New Post: Deploy task hangs

mikedouglas — Thu, 23 Dec 2010 13:59:06 GMT

Hi,

I'm glad to hear you have Team Deploy working. As for disabling RDP, I did some research and it changes some firewall settings behind the scenes. You might try temporarily disabling the firewall to see if there was something set to block it. Also, you might check the network settings and make sure the option that this computer can be seen by other computers is still enabled. With a local administrator account, can you manually get to \\testW7\admin$?

As for the hanging, I'm not sure why you are seeing the -1. I would try running PSKill manually to see if there is any more information. Also, if you log into the machine, sometimes there is a dialog box being displayed that causes it to hang.

I hope this helps,

Mike

New Post: Deploy task hangs

znakeeye — Thu, 23 Dec 2010 11:26:24 GMT

Finally got Team Deploy working here. Great! :)

However, I'm experiencing two strange problems.
1) If Remote Desktop is disabled on the target computer (tested on Windows 7 64-bit), I receive a System.IO.IOException as shown below.
2) Deploy task hangs. See log below.

#1 (Remote Desktop disabled on client):
       Task "Deploy"
         Stopping service psexesvc on testW7...
         Stopping service psexesvc on testXP...
         Stopping service psexesvc on testXP returned code:0
         Process psexesvc on testXP returned code:-1
         Process psexesvc on testXP had been terminated.
         Deleting service psexesvc on testXP...
         Deleting service psexesvc on testXP returned code:0
         In Uninstall.Execute()
         Stopping service psexesvc on testW7 returned code:0
         Process psexesvc on testW7 returned code:-1
         Process psexesvc on testW7 had been terminated.
         Deleting service psexesvc on testW7...
         Deleting service psexesvc on testW7 returned code:0
     1>C:\BuildType\TFSBuild.proj(237,5): error : Error executing CleanupPsExec: TargetMachine=testW7 KillPathFilename=c:\Program Files\PSTools\pskill2.exe:::System.IO.IOException: The network path was not found.
C:\BuildType\TFSBuild.proj(237,5): error :
C:\BuildType\TFSBuild.proj(237,5): error :    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
C:\BuildType\TFSBuild.proj(237,5): error :    at System.IO.File.Delete(String path)
C:\BuildType\TFSBuild.proj(237,5): error :    at TeamDeploy.Tasks.CleanupPsExec.Execute()

#2 (Deploy task hangs?):
     1>Target "DeployMSITargetVirtuals" in file "C:\BuildType\TFSBuild.proj" from project "C:\BuildType\TFSBuild.proj":
       Using "Deploy" task from assembly "C:\Program Files\MSBuild\TeamDeploy\TeamDeploy.Tasks.dll".
       Task "Deploy"
         Stopping service psexesvc on testXP...
         Stopping service psexesvc on testW7...
         Stopping service psexesvc on testXP returned code:0
         Stopping service psexesvc on testW7 returned code:0
         Process psexesvc on testW7 returned code:-1
         Process psexesvc on testW7 had been terminated.
         Deleting service psexesvc on testW7...
         Deleting service psexesvc on testW7 returned code:0
         Process psexesvc on testXP returned code:-1
         Process psexesvc on testXP had been terminated.
         Deleting service psexesvc on testXP...
         Deleting service psexesvc on testXP returned code:0
         Process A.exe on testW7 returned code:-1
         Process A.exe on testW7 had been terminated.
         Process B.exe on testW7 returned code:-1
         Process B.exe on testW7 had been terminated.
         Process A.exe on testXP returned code:-1
         Process A.exe on testXP had been terminated.
         Process C.exe on testW7 returned code:-1
         Process C.exe on testW7 had been terminated.
         Process B.exe on testXP returned code:-1
         Process B.exe on testXP had been terminated.
         Process D.exe on testW7 returned code:-1
         Process D.exe on testW7 had been terminated.
         Process E.exe on testW7 returned code:-1
         Process E.exe on testW7 had been terminated.
         In Uninstall.Execute()
         Process C.exe on testXP returned code:-1
         Process C.exe on testXP had been terminated.
         Process D.exe on testXP returned code:-1
         Process D.exe on testXP had been terminated.
         Uninstalling {11111111-2222-3333-4444-555555555555} on testW7 returned code:1605
         Uninstalling {11111111-2222-3333-4444-555555555555} on testW7 completed successfully.
         Process E.exe on testXP returned code:-1
         Process E.exe on testXP had been terminated.
         In Uninstall.Execute()
         Uninstalling {11111111-2222-3333-4444-555555555555} on testXP returned code:1605
         Uninstalling {11111111-2222-3333-4444-555555555555} on testXP completed successfully.
         This was the last item being logged. Waited 25 minutes and then terminated the build...

The only thing I can conclude from that is that the killing of process E.exe was not executed on testW7. I would expect the following entries:
Process E.exe on testW7 returned code:-1
Process E.exe on testW7 had been terminated.

Any ideas? Greatly appreciate your help!