Defining Job Goals with Job States
Registered by
Sarvi Shanmugham
I would like propose and implement a mechanism to use job states in the start/stop on conditions.
Today we we say start on started <JOBNAME>. This usually means the started event of <JOBNAME> as opposed to the steady state of "started" of <JOBNAME>. So If a new job was added after <JOBNAME> has already started and wanted to be run only after <JOBNAME> is already in the started state, there is no mechanism.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Sarvi Shanmugham
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)
