[#CIB-1364] Enabling a disabled trigger caused trigger to fire

Pulse

Enabling a disabled trigger caused trigger to fire

Created: 22/Jan/08 01:42 PM Updated: 24/Jan/08 09:51 AM

Component/s:

Web UI

Affects Version/s:

1.2.43

Fix Version/s:

1.2.46

Description

« Hide

I just enabled a trigger of type 'cron' (our nightly builds) and was surprised to see it trigger a build. It shouldn't have. Thinking about it I've definitely seen this before.

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Daniel Ostermeier - 23/Jan/08 12:41 AM

Hi James,

Thanks for the heads up on this. It should be simple enough to resolve (famous last words :) ) so I have scheduled it for the next patch release.

Cheers,
-Daniel

[ Permlink | « Hide ]

Daniel Ostermeier - 24/Jan/08 04:44 AM

The behaviour you are seeing is because Quartz, the internal scheduling system we are running will, by default, fire a cron trigger if a firing was missed because it was disabled / paused.

I have tweaked how we configure these cron triggers internally to stop this.

[ Permlink | « Hide ]

Daniel Ostermeier - 24/Jan/08 04:46 AM

resolved in revision 4077 and 4078

[ Permlink | « Hide ]

James French - 24/Jan/08 09:51 AM

Cheers :)