Continuum
  1. Continuum
  2. CONTINUUM-2195

adding a new schedule does not work on first activation

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.3.3 (Beta)
    • Fix Version/s: 1.3.4 (Beta)
    • Component/s: Core system
    • Labels:
      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)...
      

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Jose Morales Martinez
            Reporter:
            Brett Porter
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development