Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-13793

Build isn't triggered after reboot

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: In Progress (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      Mac OS X Jenkins 1.463 buildresult-trigger 0.6
    • Similar Issues:

      Description

      After rebooting jenkins the buildresult-trigger won't trigger a build.
      In our setup we use the buildresult-trigger to run a nightly test suite only after a build has happened during the day.
      If the server is rebooted then builds will not be triggered on the first night and will only be triggered on the second night if another build has happened during the second day.
      The polling log on the first night says that the monitored build didn't exist before. I guess this is because the plugin has no persistance? This means that after installing updates or new plugins our tests wont run for at least a day.

        Attachments

          Activity

          Hide
          gbois Gregory Boissinot added a comment -

          It is an issue that the plugin has to be take care.
          You're right, there is no change detection because Jenkins has reboot and the plugin uses only persistence in memory at the moment.
          I need to add a feature to have persistence on demand for this plugin.

          Show
          gbois Gregory Boissinot added a comment - It is an issue that the plugin has to be take care. You're right, there is no change detection because Jenkins has reboot and the plugin uses only persistence in memory at the moment. I need to add a feature to have persistence on demand for this plugin.
          Hide
          gbois Gregory Boissinot added a comment -

          Regarding this plugin, do you want have persistence for all jobs where this activated or job by job?
          In all cases, there will be an option to specify when you want to persist your data.

          Show
          gbois Gregory Boissinot added a comment - Regarding this plugin, do you want have persistence for all jobs where this activated or job by job? In all cases, there will be an option to specify when you want to persist your data.
          Hide
          tkopal Tomas Kopal added a comment -

          I would expect the plugin to behave always the same, regardless if there was a restart or not. I think that means to have persistence for all jobs where the plugin is activated.

          Show
          tkopal Tomas Kopal added a comment - I would expect the plugin to behave always the same, regardless if there was a restart or not. I think that means to have persistence for all jobs where the plugin is activated.
          Hide
          menges_ghebre Mengesteab Ghebreyesus added a comment -

          The issue is in progress for a very long time. Will it at all be resolved. For us it is not minor issue.
          Thank you.

          Show
          menges_ghebre Mengesteab Ghebreyesus added a comment - The issue is in progress for a very long time. Will it at all be resolved. For us it is not minor issue. Thank you.

            People

            • Assignee:
              Unassigned
              Reporter:
              alanbirtles Alan Birtles
            • Votes:
              6 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated: