Azure管道对同一提交触发多次问题。
- 检查触发器设定是否正确，以避免错误的设定而导致重复触发。可以参考以下代码示例：
resources: repositories: - repository: MyRepo type: git name: MyProject/MyRepo trigger: branches: - master tags: - v*
-
确认提交的唯一性，以避免重复提交。如使用“--force”强制提交就可能会发生重复提交的问题。
-
在管道中使用缓存，可以减少不必要的重复运行。可以参考以下代码示例：
steps:
-
task: [email protected] inputs: key: 'node | "$(Agent.OS)" | **/package-lock.json' restoreKeys: 'node | "$(Agent.OS)"' displayName: 'npm ci'
-
task: [email protected] inputs: key: 'node | "$(Agent.OS)" | **/*.js' restoreKeys: 'node | "$(Agent.OS)" # this creates a restore key for node, which allows us to preserve node_modules across pipeline runs regardless of whether we've updated our dependencies. displayName: 'npm run build' condition: ne(variables['Build.Reason'], 'PullRequest') # we only want to build from code changes in the master branch
-
task: [email protected] inputs: key: 'node | "$(Agent.OS)" | **/node_modules' restoreKeys: 'node | "$(Agent.OS)"' displayName: 'npm pack' condition: ne(variables['Build.Reason'], 'PullRequest') # we only want to build from code changes in the master branch
-
task: [email protected] inputs: packageType: 'npm' versionSpec: '$(PackageVersion)' feed: 'MyFeed' projectName: 'MyProject' description: 'Package description' displayName: 'npm publish'
- 多次触发管道时，可以在日志中查看是否有重复的提交记录。如果有，则需要检查提交记录的唯一