Deployer plugin vs TC 8.0.2, status alfa, alternatives?


Has anyone been sucessfully using on TC 8.0.2? I'm going to try this myself, and would love to know any bad&good experience others might have had already.

I'm also a bit concerned about the "Status   alfa" notice on the plugin's page. That doesn't sound encouraging :). Does it mean I should expect crashes, data loss or some other nice things like these?

Do you know any alternative ways for uploading TC build artifacts using SCP?

Comment actions Permalink

Hello John,

About "alfa" notice on the plugins page. It means that plugin is not mature and stable enough to call it "beta". It was not tested throughout, data formats may change, features can be removed without notice.
Plugin successfully handles basic scenarious, some bugs were already reported and fixed. Though deployment process ifself may fail, the plugin is very unlikely to cause full-scale server crash, agents shutdown or data loss. In case of bugs, feel free to report them   to TeamCity issue tracker at

Simpliest alternative with SCP capabilities would be Ant Scp task: - but you will need to create build.xml file and store it in your VCS.

Good luck!

Comment actions Permalink


Thanks, this clarifies much. Before going the deployer plugin way, I wanted to give the simple Ant SCP task a try. I would rather avoid installing any extra stuff unless really needed.

I selected "Ant" for the "Runner type" and put the following into the "Build file content" field (I guess this is as good as having a build.xml in source control?):

<?xml version="1.0"?>
<project name="quick-ant-upload" default="upload" basedir=".">
  <target name="upload">
    <scp todir=""

Such a build step fails with a following information:

[15:31:28][Step 3/3] Starting:  "C:\Program Files\Java\jdk1.6.0_45\bin\java.exe"  -DFxCopCmdFileVersion=10.0.30319.1 "-DFxCopRoot=C:\Program Files  (x86)\Microsoft Visual Studio 10.0\Team Tools\Static Analysis  Tools\FxCop" -Dagent.home.dir=C:\BuildAgent  -Dagent.ownPort=9090\TeamCity\buildAgent\work  -Dant.home=C:\BuildAgent\plugins\ant -Dbuild.number=72\TeamCity\buildAgent\temp\buildTmp  -Dteamcity.agent.cpuBenchmark=561  -Dteamcity.agent.dotnet.agent_url=http://localhost:9090/RPC2  -Dteamcity.agent.dotnet.build_id=180  -Dteamcity.auth.password=3DSURJjt7ERdLqF7rNOLxCmCumzpDDyu  -Dteamcity.auth.userId=TeamCityBuildId=180\TeamCity\buildAgent\temp\buildTmp\changedFiles8546043899420574754.txt\TeamCity\buildAgent\work\e4249c2d6a4e9e8d\TeamCity\buildAgent\temp\buildTmp\\TeamCity\buildAgent\temp\buildTmp\TeamCity\buildAgent\work\e4249c2d6a4e9e8d  -Dteamcity.buildConfName=notification-custom\TeamCity\buildAgent\temp\buildTmp\   -Dteamcity.dotnet.nunitaddin=C:\BuildAgent\plugins\dotnetPlugin\bin\JetBrains.TeamCity.NUnitAddin-NUnit   -Dteamcity.dotnet.nunitlauncher=C:\BuildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.NUnitLauncher.exe   -Dteamcity.dotnet.nunitlauncher.msbuild.task=C:\BuildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.MSBuildLoggers.dll   -Dteamcity.dotnet.nunitlauncher1.1=C:\BuildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.NUnitLauncher1.1.exe   -Dteamcity.dotnet.nunitlauncher2.0=C:\BuildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.NUnitLauncher2.0.exe   -Dteamcity.dotnet.nunitlauncher2.0.vsts=C:\BuildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.NUnitLauncher2.0.VSTS.exe   -Dteamcity.dotnet.platform=C:\BuildAgent\plugins\dotnetPlugin\bin\JetBrains.TeamCity.PlatformProcessRunner.1.1.exe  -Dteamcity.projectName=sieczka\TeamCity\buildAgent\temp\buildTmp\   -Dteamcity.runtime.props.file=D:\TeamCity\buildAgent\temp\agentTmp\ant1339456217913994994runtime   -Dteamcity.tests.recentlyFailedTests.file=D:\TeamCity\buildAgent\temp\buildTmp\testsToRunFirst2486717625687172962.txt  "-Dteamcity.version=8.0.2 (build 27482)" -classpath  C:\BuildAgent\plugins\ant\lib\ant-launcher.jar -lib  C:/BuildAgent/plugins/antPlugin/ant-runtime.jar;C:/BuildAgent/lib/runtime-util.jar  -listener jetbrains.buildServer.agent.ant.AgentBuildListener -buildfile   D:\TeamCity\buildAgent\work\e4249c2d6a4e9e8d\build5728792422698932675.tmp

[15:31:28][Step 3/3] in directory: D:\TeamCity\buildAgent\work\e4249c2d6a4e9e8d

[15:31:29][Step 3/3] upload

[15:31:29][upload] scp

[15:31:29][scp] Problem: failed to create task or type scp Cause: Could not load a dependent class com/jcraft/jsch/Logger        It is not enough to have Ant's optional JARs        you need the JAR files that the optional tasks depend upon.        Ant's optional task dependencies are listed in the manual. Action: Determine what extra JAR files are needed, and place them in one of:         -C:\BuildAgent\plugins\ant\lib         -C:\Users\sys_tcd\.ant\lib         -a directory added on the command line with the -lib argument  Do not panic, this is a common problem. The commonest cause is a missing JAR.  This is not a bug; it is a configuration problem

The problem seems to be the a missing com/jcraft/jsch/Logger class. I have ant-jsch.jar in C:\BuildAgent\plugins\ant\lib, as it came with the TC installation, but it does not contain such class. Is TC 8.0.2 lacking some jars maybe?
Comment actions Permalink


I believe, the error message speaks for itself: Teamcity bundles standart ant distribution that does not contain optional tasks' dependencies, you will have to download them manually.

Comment actions Permalink

JSch from is the missing bit.

BTW, does your Deployer plugin depend on it too?

Comment actions Permalink

Deployer plugin bundles all required libraries. You will not have to install anything but the plugin itself.


Please sign in to leave a comment.