Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

With this plugin, you can use jenkins build artifact as a repository, and deploy your build artifact with capistrano.

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 lib
Octocat-spinner-32 spec
Octocat-spinner-32 .editorconfig
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .rspec
Octocat-spinner-32 .travis.yml
Octocat-spinner-32 Gemfile
Octocat-spinner-32 Gemfile.lock
Octocat-spinner-32 NEWS.md
Octocat-spinner-32 README.md
Octocat-spinner-32 Rakefile
Octocat-spinner-32 capistrano-scm-jenkins.gemspec
README.md

Capistrano::Jenkins

Build Status Gem Version Dependency Status

Allows Capistrano to treat Jenkins as an SCM, deploying artifacts from a specified job.

Installation

Add this line to your application's Gemfile:

gem 'capistrano-scm-jenkins'

And then execute:

$ bundle

Or install it yourself as:

$ gem install capistrano-scm-jenkins

Usage

In your Capfile, you’ll need to require 'capistrano-scm-jenkins.

A sample config/deploy.rb:

set :application, 'my-sweet-app'
set :repo_url, 'http://my.jenkins.install/job/my-sweet-app'
set :deploy_to, "/home/#{fetch(:user)}/#{fetch(:application)}"

# Jenkins username & password
set :jenkins_user, 'user'
set :jenkins_pass, 'pass'

# Allow the deployment of unstable versions
# set :jenkins_use_unstable, true

# Deploy from artifact subfolder. (ex: mv zipout/#{:jenkins_artifact_path} #{destination})
# set :jenkins_artifact_path, 'archive'
#
# Deploy a single file.
# set :jenkins_artifact_file, 'my-api/target/webapp.war'
#
# Bypass SSL verification
# set :jenkins_insecure, true

maven module

For a Maven module, you should include the module name in the :repo_url:

set :repo_url,  "http://jenkins.example.com/job/example/com.example.helloworld$helloworld/"

Contributing

  1. Fork it ( http://github.com/evertrue/capistrano-scm-jenkins/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

LICENSE

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Something went wrong with that request. Please try again.