I am having problems with the fact that you cannot automatically start Scheduled Build after the same build is started manually and there are no changes.
Problem: The assembly is scheduled to be released at 3 p.m. every day, but only in case of any changes (the "Settings" parameter, even if nothing has changed, since the previous assembly has been unchecked). The problem is that if you run a manual assembly and no changes occur after it, the scheduled assembly will still be started, even if there are no changes. Below is an example below:
Scenario:
- The planned build starts today at 3am - changes to the build version to 1.0.0.1
- On the same day, some changes are checked before noon.
- The same assembly starts manually at 1 o'clock. - build version version 1.0.0.2.
- After manual assembly, no checks will be made from 1 hour.
- The next day at 3 o’clock there will be a scheduled assembly that it should not have (the version of the assembly changes to 1.0.0.3), since there have been no checks since 1 o’clock (with manual start).
The 1pm build does not even seem to be considered or taken into account.
It seems that TFS has been taking accounts since the last “scheduled build”, and not the “last completed build” (the same build definition), which in this case was called manually.
, : " - TFS , , ?"
, TFS