Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.3.3 (Beta)
-
None
Description
When the schedule was first created (with no projects assigned), it was "activated". However, after assigning a project to it, it did not fire. Editing the schedule (no changes made), caused it to fire on the assigned project. The log is as follows:
2009-04-22 20:03:51,005 [btpool0-1] INFO org.apache.maven.continuum.build.settings.DefaultSchedulesActivator - Activating schedule minutely
2009-04-22 20:37:13,488 [btpool0-7] INFO org.apache.maven.continuum.build.settings.DefaultSchedulesActivator - Deactivating schedule minutely
2009-04-22 20:37:13,488 [btpool0-7] INFO org.apache.maven.continuum.build.settings.DefaultSchedulesActivator - Stopping active schedule "minutely".
2009-04-22 20:37:13,488 [btpool0-7] INFO org.apache.maven.continuum.build.settings.DefaultSchedulesActivator - Activating schedule minutely
2009-04-22 20:37:13,494 [btpool0-7] INFO org.apache.maven.continuum.build.settings.DefaultSchedulesActivator - minutely: next fire time ->Wed Apr 22 20:38:00 EST 2009
2009-04-22 20:38:00,019 [continuumScheduler_Worker-4] INFO org.apache.maven.continuum.build.settings.DefaultSchedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (minutely)...
Actually Continuum add a schedule is associated with a buildDefinition or purge process. Then you need an enable disable previously if it was not associated with a project. I think there are two possible solutions:
1.- When whe updated or add a new build definition or purge process we would check if associated schedule jobs is in queuue (pending to execute) and enable/disable it.
2.- Always (active = true) enqueue 2 jobs, first for buildProcess and second for purge process. They check if there are associated elements to execute process.
What solution do you think is better?