Deployer plugin

Skip to end of metadata
Go to start of metadata

General Info

Vendor Nikita Skvortsov
License Apache 2.0
Type open-source
Status alfa

Description

Adds basic deployment functions to the supported targets (see below).

Usage

In build configuration settings, new runners will be available for the build steps.
New runners include:

  • SMB Deployer - upload files to Windows shares via SMB protocol
  • FTP Deployer - upload files to FTP servers
  • SSH Deployer - upload files via SSH (using SCP or SFTP protocols)
  • SSH Exec - execute arbitrary remote commands using SSH
  • Tomcat Deployer - deploy WAR application archives to a remote Tomcat instance (requires Manager webapp installed in the target Tomcat server)

When configuring file for upload, the same patterns can be used as in "Artifacts Path" section of "General Settings" page. Packaging files into zip/tgz archives is also supported.

Artifact paths pattern targets are always interpreted as relative paths. To upload files to some absolute destination, please specify root in "Target" field. Examples:

SSH (SCP or SFTP) 192.168.0.1:/
192.168.0.1:/home/userName/junk
FTP 192.168.0.1:21/
192.168.0.1:21/var/log

Compatibility

TeamCity 7.0+
Oracle JDK 1.6 or OpenJDK 1.7.0_07 and later.

Sources

https://bitbucket.org/nskvortsov/deployer/src

Issue tracker

https://bitbucket.org/nskvortsov/deployer/issues

Continuous Integration

Current build status is
Detailed CI status page

Download

deploy-runner.zip

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

5 Comments

comments.show.hide

  1. Dec 12, 2012

    Ivan Boyko

    Brilliant idea. We especially like SSH runners. Wish you luck in development and hope you'll progress it to production level soon :)

  2. Dec 13, 2012

    Yuri Trukhin

    need Glassfish deployer too. Cool idea. Want to deploy via intellij project run configuration remote glass fish

  3. Apr 15, 2013

    naik

    is it possible to provide multiple hosts comma separated?

    1. Apr 15, 2013

      Nikita Skvortsov

      No, you can only have one target host at a time.

      Could you explain, why do you need to deploy same artifacts to a number of lockations simultaneously?

      As a work around, you can use build parameters to store common information (like username/password/artifact paths) and create several build steps that only differ in target feild.

  4. Apr 15, 2013

    naik

    Thanks for prompt reply,  I did created build steps that differs on target host but it is not efficient when deployment needs to be selective based on specific Env where each target environment may have 10/20 hosts, would be nice to use comma separated list or something similar and provide it to deployer target.