jenkins rollback和command

Publish Over SSH Plugin

Features
SCP - Send files over SSH (SFTP)
Execute commands on a remote server (can be disabled for a server configuration, or for the whole plugin)
Use username and password (keyboard-interactive) or public key authentication
Passwords/passphrases are encrypted in the configuration files and in the UI
SSH SFTP/ SSH Exec can be used as a build step during the build process (Freestyle and Matrix projects)
SSH before a (maven) project build, or to run after a build whether the build was successful or not (see Build wrappers below)
The plugin is “promotion aware” (send files directly from the artifacts directory of the build that is being promoted) see Promotions
Optionally override the authentication credentials for each server in the job configuration (or provide them if they have not been provided for that server in the global configuration)
Optionally retry if the transfer of files fails (useful for flakey connections)
Enable the command/ script to be executed in a pseudo TTY

Build wrappers
There will be two new options in the Build Environment section of the job configuration

Send files or execute commands over SSH before the build starts
This allows SSH to be used before a build begins, but after the workspace has been configured and source checked out
Most useful for maven project types
Send files or execute commands over SSH after the build runs
As long as the build was attempted, this will run after the build finishes, and will run whether the build is successful or not
This allows cleanup or shutdown of services started before or during the build
Use the publisher (Send build artifacts over SSH in Post-build Actions) to publish build artifacts from succesful builds

[https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+SSH+Plugin]

====================

ArtifactDeployer Plugin

Features
Copies build artifacts from the workspace to a remote location shared on the build processor node
Provides links to archived artefacts from the job status page
Deletes on demand archived artifacts when the build is removed

How to rollback or redeploy a previous build
There may be several ways to accomplish this, but here is one suggested method:

Install the Copy Artifact Plugin
Create a new job that you will trigger manually only when needed
Configure this job with a build parameter of type “Build selector for Copy Artifact”, and a copy artifact build step using “Specified by build parameter” to select the build.
Add a post-build action to deploy the artifact that was copied from the other job
Now when you trigger this job you can enter the build number (or use any other available selector) to select which build to redeploy. Thanks to Helge Taubert for this idea.
[https://wiki.jenkins-ci.org/display/JENKINS/Deploy+Plugin]