History of Nested Jobs in Rundeck

[Shawn Kielty]

SO -- if I have a Job A which calls Jobs B and C -- a history list will be maintained for job A, but no history is present for the execution of jobs B an C.  Is this the original intent?  -- it seems a bit counter intuitive IMHO. 

[Greg Schueler]

Hi Shawn,

Yes, that is currently the mechanism, and I agree it's not intuitive.  It also doesn't track stats (e.g. success/failure percentage) for the nested jobs, or perform Notifications.

One issue is how to handle the log output, which currently ends up in Job A's logs. Would you expect to be able to navigate to job B and see only its output for a past execution that was triggered within another job? Or should it merely link back to Job A's execution?

We are also looking to modify the way jobs and workflows are defined.  Essentially workflows would become independent of Jobs.  This is a feature that has been on the roadmap for a while.  (The way job references work now is that it essentially incorporates the workflow defined in Job B&C as if they were part of job A).

[Matthew Thompson]

Sorry I know this is an old thread but it's exactly an enhancement I'd like to see.

We have some nightly jobs which have other jobs nested in and it would be a lot more helpful for reporting purposes if the DB tables stored information on those nested jobs.

Has any work progressed on this or is any work planned ?

Cheers,

Matt.