Hi!
You’re right. The other way is via Rundeck API: get the projects, then the jobs ID by the user, and then the exec info. I made a script example that does this in JSON format (requires jq tool), feel free to use and improve it:
#!/bin/sh cat <<EOF Usage: $0 username Example: $0 bob EOF if [ $# -eq 0 ] then echo "The user wasn't supplied" else # protocol protocol="http" # basic rundeck info rdeck_host="localhost" rdeck_port="4440" rdeck_api="46" rdeck_token="As4F70JTdEYZOyXP9SDv3d3KGFTrIdC9" for i in $(curl -s --location "http://$rdeck_host:$rdeck_port/api/$rdeck_api/projects" --header "Accept: application/json" --header "X-Rundeck-Auth-Token: $rdeck_token" | jq -r .[].name); do for k in $(curl -s --location "http://$rdeck_host:$rdeck_port/api/$rdeck_api/project/$i/jobs" --header "Accept: application/json" --header "X-Rundeck-Auth-Token: $rdeck_token" --header "Content-Type: application/json" | jq -r .[].id); do for q in $(curl -s --location "http://$rdeck_host:$rdeck_port/api/$rdeck_api/job/$k/executions" --header "Accept: application/json" --header "X-Rundeck-Auth-Token: $rdeck_token" --header "Content-Type: application/json" | jq -r '.executions[] | "\(.id) \(.user)"' | grep $1 | cut -d ' ' -f1); do curl -s --location -g "http://$rdeck_host:$rdeck_port/api/$rdeck_api/execution/$q" --header "Accept: application/json" --header "X-Rundeck-Auth-Token: $rdeck_token" --header "Content-Type: application/json" | jq done done done fiRegards.