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" <[email protected]> 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
