Azure devops 编写Azure DevOps构建计划脚本会产生意外结果

Azure devops 编写Azure DevOps构建计划脚本会产生意外结果,azure-devops,Azure Devops,这个问题与 鉴于: 设置构建时间表的脚本在东部时间上午7:59运行 该时间表为每5分钟一次,而不考虑master上EST每天的变化 据费德勒说: 响应标题包含日期:2019年11月6日星期三13:00:49 GMT PUT请求包含以下JSON片段(请参见下面的文本): PUT请求响应: 下面是与计划相关的JSON请求主体片段: "schedules": [ { "branchFilters":

这个问题与

鉴于:

  • 设置构建时间表的脚本在东部时间上午7:59运行
  • 该时间表为每5分钟一次,而不考虑master上EST每天的变化
  • 据费德勒说:
  • 响应标题包含日期:2019年11月6日星期三13:00:49 GMT
  • PUT请求包含以下JSON片段(请参见下面的文本):
  • PUT请求响应:
下面是与计划相关的JSON请求主体片段:

 "schedules":  [
                   {
                       "branchFilters":  [
                                             "+refs/heads/master"
                                         ],
                       "startMinutes":  59,
                       "scheduleOnlyWithChanges":  false,
                       "startHours":  7,
                       "timeZoneId":  "Eastern Standard Time",
                       "daysToBuild":  127
                   },
                   {
                       "branchFilters":  [
                                             "+refs/heads/master"
                                         ],
                       "startMinutes":  4,
                       "scheduleOnlyWithChanges":  false,
                       "startHours":  8,
                       "timeZoneId":  "Eastern Standard Time",
                       "daysToBuild":  127
                   },
                   {
                       "branchFilters":  [
                                             "+refs/heads/master"
                                         ],
                       "startMinutes":  9,
                       "scheduleOnlyWithChanges":  false,
                       "startHours":  8,
                       "timeZoneId":  "Eastern Standard Time",
                       "daysToBuild":  127
                   },
...
相应的响应JSON片段是:

"schedules": [
    {
        "branchFilters": [
            "+refs/heads/master"
        ],
        "timeZoneId": "Eastern Standard Time",
        "startHours": 7,
        "startMinutes": 59,
        "daysToBuild": "all",
        "scheduleJobId": "21a1da8a-e508-40ad-8716-d3e1483f05d7",
        "scheduleOnlyWithChanges": false
    },
    {
        "branchFilters": [
            "+refs/heads/master"
        ],
        "timeZoneId": "Eastern Standard Time",
        "startHours": 8,
        "startMinutes": 4,
        "daysToBuild": "all",
        "scheduleJobId": "425eaa93-9f35-4dcb-aeb0-437479caab8d",
        "scheduleOnlyWithChanges": false
    },
    {
        "branchFilters": [
            "+refs/heads/master"
        ],
        "timeZoneId": "Eastern Standard Time",
        "startHours": 8,
        "startMinutes": 9,
        "daysToBuild": "all",
        "scheduleJobId": "a109daa2-f65b-4792-b599-594fdf1363ca",
        "scheduleOnlyWithChanges": false
    },
...
到目前为止还不错。考虑到所有这些,我的期望是在东部标准时间找到7:59开始的时间表(因为这就是我要问的,并且得到的答复证实了这一点),第一个时间表在东部标准时间8:04开始

然而,情况并非如此。观察实际结果:

  • GUI中显示的计划: ...
  • 以及生成历史记录报告的实际计划生成:
如预期的那样,时间表以5分钟的间隔覆盖了整个24小时范围。但是:

  • 为什么第一次计划的构建发生在东部时间上午9:04而不是上午8:04
  • 为什么GUI中的日程安排在凌晨4:14开始

  • 一小时后,猜它应该和夏令时DST有关。一小时后,猜它应该和夏令时DST有关。
    "schedules": [
        {
            "branchFilters": [
                "+refs/heads/master"
            ],
            "timeZoneId": "Eastern Standard Time",
            "startHours": 7,
            "startMinutes": 59,
            "daysToBuild": "all",
            "scheduleJobId": "21a1da8a-e508-40ad-8716-d3e1483f05d7",
            "scheduleOnlyWithChanges": false
        },
        {
            "branchFilters": [
                "+refs/heads/master"
            ],
            "timeZoneId": "Eastern Standard Time",
            "startHours": 8,
            "startMinutes": 4,
            "daysToBuild": "all",
            "scheduleJobId": "425eaa93-9f35-4dcb-aeb0-437479caab8d",
            "scheduleOnlyWithChanges": false
        },
        {
            "branchFilters": [
                "+refs/heads/master"
            ],
            "timeZoneId": "Eastern Standard Time",
            "startHours": 8,
            "startMinutes": 9,
            "daysToBuild": "all",
            "scheduleJobId": "a109daa2-f65b-4792-b599-594fdf1363ca",
            "scheduleOnlyWithChanges": false
        },
    ...