Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361217 - Need a way to record why/what/who triggered execution of a job
Summary: Need a way to record why/what/who triggered execution of a job
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: gyrex (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Mike Tschierschke CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-18 04:26 EDT by Mike Tschierschke CLA
Modified: 2018-03-19 11:59 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Tschierschke CLA 2011-10-18 04:26:43 EDT
During the work with the provisional jobs api we noticed, that we need to improve the traceability of actions made on jobs. So we have extend the IJobManager queueJob and cancelJob methods with a mandatory field 'trigger', that simply extends the job history data. The job history also has to provide IStatus objects instead of a pair of severity and result.
We also decided, that a single schedule entry must have the ability to be disabled regardless the enclosing schedule is running.
Comment 1 Gunnar Wagenknecht CLA 2011-10-18 08:32:17 EDT
+1
Comment 2 Gunnar Wagenknecht CLA 2011-11-01 12:49:38 EDT
Marking fixed.