Laur IVAN

Rundeck – Speeding Up Even More the Cleaning Process

Posted by in IT, Tutorial

As I was running the script, I’ve noticed it ran very slow. I have left it for a few days to run (700K executions), I’ve noticed the speed increased linearly over time. As Rundeck has both DB and files to store its data, it looked to me that it was the file system which was the slow part. Sure enough, when I tried to access the directory where the execution data was stored, it was slow – 1.4M files would take a while to get organised :) To short out…read more

Delete Executions in Rundeck – Wrapping it all Up

Posted by in IT, Software, Tutorial

The previous posts have built the components to allow us to get projects, jobs, executions and remove executions from a Rundeck instance via its API. Now, we can just wrap them up :) The list of packages we need is:

For convenience, I’ve declared a bunch of constants we can use throughout the project:

As we already have all the helper functions defined, we only need to wrap them in a convenient execution command:

The logis is fairly simple: Get the list of projects For each project,…read more

Remove Executions in Rundeck

Posted by in IT, Tutorial

TL;DR: You have to get the executions’ list and remove the appropriate ones using hte API. Once we’ve managed to get the list of job executions, we can use the API to remove the relevant executions. The command is rather simple:

This method requires: server – the Rundeck’s server address port – the port on which we can connect to the Rundeck server api_key – the API key execution_ids – an array of valid execution IDs The function will try to remove all execution IDs in one go, since…read more

Get Job Executions in Rundeck

Posted by in IT, Tutorial

Following the previous articles, we are now in position to query job executions. The query is done via API as well. As a job can have an arbitrary number of executions, it’s advisable to use pagination. The code follows the same lines as the one in the previous entries:

This function builds the URL for the call and returns an XML string. Its parameters are: server – the rundeck server port – the rundeck server’s port api_key – the api key for rundeck job_id – one of the job…read more