Bug 4364 - Interaction of start-limit and allow-start-if-complete
Interaction of start-limit and allow-start-if-complete
Status: CLOSED WORKSFORME
Product: jbatch
Classification: Unclassified
Component: source
1
PC Windows
: P5 normal
: ---
Assigned To: cvignola
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-21 12:47 UTC by ScottKurz
Modified: 2013-01-16 15:55 UTC (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 ScottKurz 2012-11-21 12:47:46 UTC
One could imagine hitting the start-limit for a given step, not because of repeated failures, but because allow-start-if-complete is set to 'true'.

Or should that not count against start-limit?  

If not, then in spite of the conclusion of Bug 4266, we should probably go back to considering this a "restart limit" not a limit on the number of executions.

We could reserve the '0' setting to mean, "cannot be run on restart" and we could use the absence of the attribute altogether to mean "no limit".
Comment 1 cvignola 2012-12-06 23:42:44 UTC
You get what you get.   If you specify allow-start-if-complete and a start-limit, the step can only start start-limit times.  Start-limit=0 still means no limit.