[
https://issues.jenkins-ci.org/browse/JENKINS-13793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163461#comment-163461
]
Gregory Boissinot commented on JENKINS-13793:
---------------------------------------------
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.
> Build isn't triggered after reboot
> ----------------------------------
>
> Key: JENKINS-13793
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13793
> Project: Jenkins
> Issue Type: Bug
> Components: buildresult-trigger
> Environment: Mac OS X Jenkins 1.463 buildresult-trigger 0.6
> Reporter: Alan Birtles
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
