SCP plugin


This plugin allows you upload some build artifacts to the repository sites using SFTP (SSH) protocol. First you should define SCP hosts on hudson global config page. After that you can refer to this hosts using select list. See picture for global config:


After entering username/password automatic logon check is performed to see if you entered it correctly.
Root repository path must exist before you can reference it and should be accessible by user who do publish of files.


Then per job you can enable publishing of build artifacts:

source points to files which will be uploaded. You can use ant includes syntax, eg. folder/dist/*.jar. Path is constructed from workspace root.
  Note that you cannot point files outside the workspace directory. For example providing: ../myfile.txt won't work...
destination points to destination folder on remote site. It will be created if doesn't exists and relative to root repository path.
You can define multiple blocks of source/destination pairs.

Changelog

Version 1.5.2
  • Fix for issue #2609 : version 1.5.1 of the SCP plugin is broken for "password only"
    authentication
Version 1.5.1
  • Enhancement , support for public key authentication (issue #1269)
  • Enhancement, works now with Maven2 jobs (issue 1845)
Upcoming Version 1.5
  • Improved error diagnosis when the specified file pattern didn't match anything.
Version 1.4 (2008/07/23)
Version 1.3
  • fixed bug with subdirectories creation
Version 1.2

Labels

  Edit Labels
  1. Feb 15, 2008

    Anonymous says:

    Can you access other job's lastSuccessful?  I want to create a new schedule...

    Can you access other job's lastSuccessful?  I want to create a new scheduled job that grabs the last successful build artifact of a particular job.  Is this possible?

    1. Apr 24, 2008

      Bartek Zdanowski says:

      Nope, you cannot. I spent some time debbuging SCP Plugin. You cannot access file...

      Nope, you cannot. I spent some time debbuging SCP Plugin. You cannot access files outside workspace. I need version that allows it and maybe I'll fix it and put new plugin somewhere. Or Ramil will do it?

  2. Jun 24

    Trond Andersen says:

    Does this plugin work on Windows with Cygwin installed? If so this should probab...

    Does this plugin work on Windows with Cygwin installed? If so - this should probably be mentioned on this Confluence page.

  3. Aug 22

    Luke Alford says:

    If you only have a single artifact you want to copy somewhere, are there any tho...

    If you only have a single artifact you want to copy somewhere, are there any thoughts to adding the ability to rename said artifact?  Near as I can tell, the destination only allows a relative directory path and there's no way to include a new file name.  This would be a very useful feature to me since I am using this tool to copy an artifact that has a version number in the file name (for QA and production) as well as for my development automated testing tool that would like to be version agnostic (so I don't have to change the automated tester every time the artifact version changes).

    I'm thinking something like the following, but I haven't grabbed the source yet to find out what might be involved in doing this.

    artifact name = product-1.0.ear

    source: workspace/build/artifacts/*

    destination: qa/product/1.0/product-1.0.ear

    destination: dev/product/trunk/product-trunk.ear

    (where product-*.ear is the file name, not a folder)

  4. Sep 02

    Hakan ERDOĞAN says:

    This plugin is very useful, it runs on a freestyle software project but fails on...

    This plugin is very useful, it runs on a free-style software project but fails on a maven project.

    Actually it never tries to run on a maven project, no log, no process.

    Is there a solution for this?