Thoughts on Job method for creating history entries

[nrusch]

I just noticed that changes to job attributes (e.g. priority) via scripts don’t leave any entries in the job history. Now, I don’t think the solution here is for these to be created automatically by every scripting operation (since that would no doubt negatively affect performance), but I was thinking it might be handy to have a job method for adding a history entry. This isn’t super critical, but for things like the Priority Offset script, or changes made by an external wrangling algorithm, it might be nice to be able to actually choose to leave some footprints.

Thoughts on this?

[rrussell]

Hey Nathan,

The RepositoryUtils class has AddJobHistoryEntry, AddRepositoryHistoryEntry, and AddSlaveHistoryEntry functions that you can use to log your own history entries.

Looks like the standalone python api (and therefore the webservice) supports this as well, although it appears that the webservice options aren’t documented…

Cheers,
Ryan

[nrusch]

Ah damn, of course I overlooked it… Sorry, I still never really know where to look for functions before requesting duplicate functionality. Intuitively that would make the most sense to me as a Job method, so that’s the only place I thought to check. Thanks for the info!