Skip to content

Commit

Permalink
add trigger doc
Browse files Browse the repository at this point in the history
  • Loading branch information
vbehar committed Sep 14, 2011
1 parent ea155df commit fc19e75
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 1 deletion.
1 change: 1 addition & 0 deletions README
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@ Jenkins RunDeck plugin
http://wiki.jenkins-ci.org/display/JENKINS/RunDeck+Plugin

This plugin is a Jenkins Notifier (Publisher) that will talk to a RunDeck instance (via its HTTP API) to schedule a job execution on RunDeck after a successful build on Jenkins.
It is also a Jenkins Trigger, that will schedule a build on Jenkins after a job execution on RunDeck (using RunDeck WebHook Notification).
In addition, it turns Jenkins into an "Option provider" for RunDeck, if you want to use your Jenkins build artifacts as an option to a RunDeck job.

We use it to do a 0-click deployment : from commit to deploy, automatically. Jenkins build the project, and RunDeck deploys it. This plugin does the link between these 2 tools.
Expand Down
3 changes: 2 additions & 1 deletion src/main/resources/index.jelly
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
<div>
This plugin is a Notifier (Publisher) that will talk to a <a href="http://www.rundeck.org">RunDeck</a> instance
(via its HTTP API) to schedule a job execution on RunDeck after a successful build on Jenkins.<br />
It is also a Jenkins Trigger, that will schedule a build on Jenkins after a job execution on RunDeck (using RunDeck WebHook Notification).<br />
In addition, it turns Jenkins into an <a href="http://rundeck.org/docs/RunDeck-Guide.html#option-model-provider">Option provider</a>
for RunDeck, if you want to use your Jenkins build artifacts as an option to a RunDeck job.
</div>
</div>

0 comments on commit fc19e75

Please sign in to comment.