Release Automation

  • 1.  Put file (SSH) - explained

    Posted Mar 12, 2014 02:05 PM

    the put file through SSH action type has some great capabilities, but the error messages and troubleshooting might be a bit cumbersome. Let me try to summarize how the action type works for both "put folder" as well as "put file" through SSH.

    Copy Folder content

    This action does:

    • Copy the full source folder content to the target folder on the remote machine through SSH
    • The source folder name will not be created in the target. In the example below, “mysourcefolder” will not be created under ../folder2/, only the content of mysource folder will be copied.
    • The target folder does not need to exist – it will be created but only for 1 level deep. In the example below, /rootfolder/folder1/ must exist already. Only folder2 will be created, and the content of mysourcefolder will be copied into it.
    • All content from the mysourcefolder will be copied into folder2: this includes any files directly under mysourcefolder as well as any (n-level deep) subfolders and files in those subfolders

    It does not:

    • The action does not work when the content of mysourcefolder exist already in the target folder – remove the target folder before using this action type.
    • The action type does not work when you try to create new multiple nested folders in the target location. In the example below, the action will fail if neither /folder1/ and /folder2/ do not exist … it can only create 1 new folder deep, not nested folders.
    •  The action type cannot be used to “overwrite” existing files and folders. It actually tries to create it again (in nested subfolders) and will ultimately fail if you try it several times. Remove the target folder before using this action

    Copy a file

    This action does:

    • Copy the file from the source location to the target location on the remote machine through SSH
    • It does support renaming of the file while copying it: example you can copy the file myfile.txt and name it newfilename.txt in the target file path. The file will be copied and renamed to newfilename.txt
    • It does support overwrite. If the target file exists already (unaltered or changed), the action will replace the file with the source file.

    It does not:

    • The target folder must exist already.. In the example below, /rootfolder/folder1/folder2/ must exist already, otherwise the action fails.



  • 2.  RE: Put file (SSH) - explained

    Posted Apr 23, 2014 05:01 PM

    Thank you Benny for posting this helpful Tech Tip!
    Mary



  • 3.  Re: Put file (SSH) - explained

    Posted Apr 19, 2017 08:19 AM

    In this action, where should be the agent installed, is it on staging server or target server. Also where should be the keystore file be placed?



  • 4.  Re: Put file (SSH) - explained

    Broadcom Employee
    Posted Jun 20, 2018 10:57 AM

    Hi Dada,

     

    For the Put File (SSH) action, the agent would be needed on the system with the source file/folder. The keystore file can be anywhere on that system that the agent id (user who owns agents files and starts the agent process) has access to. Keystore file is not a requirement. It is only necessary if the target machine does not allow passwords to be used to establish an SSH connection.

     

    Kind regards,

    Gregg



  • 5.  Re: Put file (SSH) - explained

    Posted Jun 19, 2018 02:39 PM

    could anyone assist on this?