I've got new information in case it helps. We've noticed the problem on a subset of code analysis jobs, i.e. they wouldn't run as scheduled. However, at one point, Jenkins stopped listing these jobs in the web interface altogether. I checked the <jenkinsdir>/jobs folder on the server and all the jobs were there and there is no obvious difference between the jobs which disappeared from the UI and the ones which remained. Restarting Jenkins was enough to (temporarily?) resolve the issue.
Does this remind anyone of similar Jenkins behaviour they've seen? Cheers, Tomislav El día 10 de abril de 2012 17:18, Tomi N/A <hef...@gmail.com> escribió: > Anyone? Is this something for the Jenkins issue tracker, has anyone > encountered such behaviour? > > Cheers, Tomislav > > El día 5 de abril de 2012 12:40, Tomi N/A <hef...@gmail.com> escribió: >> Hi Jan, >> >> thanks for your answer. I'm afraid I don't understand what you mean by >> "reloading the configuration from disk". >> >> Anyway, I triggered a job (Job A) manually and it succeeded. >> >> I also changed the cron schedule of another job (Job B) from "50 1 * * >> *" to "10 * * * *" and nothing happened at 11:10. I then manually >> started Job B and it succeeded, but the scheduled build was not >> triggered at 12:10. >> >> Earlier today (before these manual tests) I checked the job workspace >> and could confirm that all files are at least 6 days old although >> normally at least some files should be younger than 24 hours. Checking >> the workspace now I can see files changed an hour ago (as expected). >> >> So, "build periodically" does not seem to build periodically. What can >> I do to fix it? >> >> Cheers, >> Tomislav >> >> El día 5 de abril de 2012 00:33, Jan Seidel <wakkal...@gmail.com> escribió: >>> Hi Tomislav, >>> >>> normally does a not correct report of the status happen if the >>> configuration is reloaded from disk. In that case would the build it >>> self also not appear in the build history. >>> Otherwise I would assume that the build did not start. Kick it off >>> manually to validate the jobs function it self and then change the >>> cron trigger to a time where you can supervise in case the manual >>> build did work. >>> >>> Take care >>> Jan >>> >>> On 4 Apr., 14:12, "Tomi N/A" <hef...@gmail.com> wrote: >>>> Hi everyone, >>>> >>>> I have jobs configured to build periodically (e.g. "30 3 * * *", every >>>> day at 3:30) and it reports the last success 5 days ago and last >>>> failure "N/A"...has anyone encountered such a problem? >>>> >>>> Can it be that the job simply doesn't get triggered or that the "last >>>> success/failure" isn't reported properly? >>>> >>>> Cheers, >>>> Tomislav
