Automated Sechdule not being followed?

Guest

I have an Automatic Build set for every 5 hours, from 2am to 6pm.
Based on my understanding from the documentation here, its 5 hours after the initial start time, and 5 hour increments after that until the end time.

So it should be at 7am, noon and 5pm.
The actual times last night were 6pm, 3am and 8am

I do know that when I promote builds using SQL to kick off many at once, I have to add 5 hours to my execution/promotion time due to a server time zone difference, I think. (it use to be 4 hours until daylight savings kicked in a few weeks ago)

Is there some obvious reason why these times are not making sense? Today I set up a few more to kick off every hour and they are working as expected, will see if they stop at 4pm as I desired.

Thanks,
Dan

Product: BuildMaster
Version: 4.5.2

Guest

As of BuildMaster v4.0, dates and times are stored in the BuildMaster database in UTC format, so it's possible there is either a missing conversion, or a double conversion taking place here... we will look into it - I'm guessing it has to do with the fact that the schedule date isn't stored directly as a time in the database, but rather as minutes relative to midnight.

Guest

Update:

The 5 hour delayed build has not executed since 8AM yesterday (26 hours ago), I was at least hoping to see it follow the same bad schedule of 6pm, 3am and 8am, but neither of those happened.

The one I have running hourly is set for 4:30 am to 5:30pm (offset by a half hour so they build out the imported deployables before other applications reference them on the hour). It ended last night at 5:30pm, and started back up at 4:30am, perfectly!!! :)

So the bug is not universal it seemed, probably has to do with trying to carry over a value across midnight, hope this helps you guys.

My work around will be to have it kick off more often, or I might just set up 3 individual automated builds each running just once a day.

(Also I am on version 4.4.7, not the 4.5 beta)

Guest

So I found out some more details. It did try to kick off some deployments for the 5 hour one, but had some errors:

Error executing scheduled build Integration (ID=1) for Application (ID=32): System.Data.SqlClient.SqlException (0x80131904): 500001642HandleError3050000161Builds_PromoteBuild46Cannot promote build. Deployables with dependencies (including imported deployables) cannot be promoted to their final env

Makes perfect sense, I have to Force the promotion when I do it by hand because I don't like my Imported applications to be marked as "Deployed" because its an ever-evolving perpetual release.

I added a fake step after the one I plan to deploy to, but I don't know if it will work as I expect. The Environment and Workflow setup is a hair confusing. Will find out soon enough what happens.

However this brings up a good point about the Automation, can we have a way to force it past certain checks/approvals?

Thanks!

Guest

The fake step is the way to go here since you can't force past the "deployables with dependencies" warning anyway. The only reason it's there is because it is almost certainly an error to build against a specific dependency (such as an SDK) and then release the dependent software using the SDK, but then do another build of the same release of said SDK which could break compatibility.