Tuesday, April 12, 2016

RunDeck Introduction / Jenkins & RunDeck Integration

Introduction about RunDeck:
-   - RunDeck can be used to automate routine operational procedures, automating tasks on multiple nodes
- - Scheduling Jobs, to give access to run specific jobs without giving the access to Servers etc.,
- - Rundeck's website says "Turn your operations procedures into self-service jobs.
                Safely give others the control and visibility they need."
- - GUI & CLI Combination- able to run it without clients agents, remote execution with SSH, Flat File Config structure.
- - To run jobs and tasks remotely, either adhoc or at specific time and capture results.
- - For Data Center Automation, Allows to trigger jobs by the Scheduler or on demand using the web interface or API.

- - Custom workflows, end to end orchestration across local or remote servers, cross-platform etc.,

Jenkins & Run Deck Integration

1) In Jenkins, 
    Install the required plugins for "RunDeck" in Jenkins
Click "Manage Jenkins" => "Manage Plugins" => Click on "Available" Option.

2)  Click "Manage Jenkins => Configure System => Search for RunDeck in the Jenkins Page.
As the plugin is installed the RunDeck options appears in this page.
Add "Run Deck" options as per the below screenshot.

3) RunDeck Options
    URL :  
       Provide the URL of the RunDeck based on the server it is installed, Default Port for RunDeck is 4440.
   Login : admin(Default Value)
   Password : admin(Default Value)
   Test Connection : Click on this once you  provide above details to check connection to RunDeck Server

4) Configure Jenkins Job for RunDeck Job Triggering:

5) In Configure Jenkins Job:

Post Build Step: Select "RunDeck" from dropdown.

6) From RunDeck: Copy the Job related "UUID" as shown below into use it in Jenkins.

7) Provide the options as below: UUID to trigger etc.,

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.