Hi since upgrading (6.10.2), we have noted that our weekly builds are not triggering. We have approx 50 builds that are scheduled to run weekly each Sunday at 2am. Since upgrading we noted that these triggers are not firing. Each build has 2 triggers * "Bitbucket Server repository triggered" * "Scheduled" As part of the upgrade testing we fired them of manually and they run through to completion perfectly. We have also tested the Bitbucket server repository triggers. This are working also. Not sure why but for the last 2 Sundays they have not triggered. I have not seen `System Errors` reported. What are my next steps to trouble shoot?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Scheduled plans are not triggering after upgrade to 6.10.2

Simon Hooper_2kqdki

Hi since upgrading (6.10.2), we have noted that our weekly builds are not triggering.

We have approx 50 builds that are scheduled to run weekly each Sunday at 2am. Since upgrading we noted that these triggers are not firing.

Each build has 2 triggers

"Bitbucket Server repository triggered"
"Scheduled"

As part of the upgrade testing we fired them of manually and they run through to completion perfectly. We have also tested the Bitbucket server repository triggers. This are working also.

Not sure why but for the last 2 Sundays they have not triggered. I have not seen `System Errors` reported. What are my next steps to trouble shoot?

Accepted answers

Jimmy Seddon

Hi @Simon Hooper,

Have you looked in the looked at the atlassian-bamboo.log file in the 'logs' folder within the Bamboo_Home directory on your Bamboo server? Specifically around the 2am time frame to see if any errors were reported when trying to run the scheduled trigger?

That would be the first place I would start.

I hope that helps!

-Jimmy

All comments

Jimmy Seddon

Hi @Simon Hooper,

That would be the first place I would start.

I hope that helps!

-Jimmy

Simon Hooper_2kqdki

Ok, we think we identified the issue. What happened at exactly 2am this Sunday? Daylight savings.

The server clock switched to 3am on the tick after 1:59:59am thus 2am never happened and the builds could not trigger. This was evident in the log file as the time stamps jumped 2am completely. Many thanks.

I dare say next Sunday will trigger fine.

Jimmy Seddon

Hey Simon,

I'm glad you found a good lead on the answer. To avoid that in the future is is possible to change the schedule time to either 1am or 3am?

-Jimmy

Simon Hooper_2kqdki

I have put this recommendation to the team who owns these plans. Many thanks.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo