英文:
What is in a Azure DevOps PR artifact?
问题
我有两个分支，develop 和 feature/cool_feature。当我创建一个PR来将feature/cool_feature合并到develop时，我们的Azure DevOps会自动运行一个管道用于这个PR。
我的假设是生成的构建包含feature/cool_feature和develop的当前状态。这是正确的吗？
我查看了几个页面，但似乎找不到明确的答案：
- https://learn.microsoft.com/en-us/azure/devops/repos/git/pull-requests?view=azure-devops&tabs=browser
- https://learn.microsoft.com/en-us/azure/devops/repos/git/about-pull-requests?view=azure-devops
- https://learn.microsoft.com/en-us/azure/devops/pipelines/release/deploy-pull-request-builds?view=azure-devops
我怀疑的原因是因为我们正在审查这个项目的测试策略。当确定我们是否应该在完成PR后测试PR构建和develop构建时，我们讨论了PR构建与“合并后”develop构建不同的可能性（两者都使用相同的管道）。还要考虑是否应该强制要求在完成PR之前将目标分支（例如我的develop）合并到源分支（feature/cool_feature）中。Azure似乎不强制执行此操作，它只检查合并冲突。
编辑
我找到了这个问题：https://developercommunity.visualstudio.com/t/pr-build-fails-but-branch-build-succeeds/1194209
这似乎确认了我的假设。
英文:
I have two branches, develop and feature/cool_feature. When I create a PR to merge feature/cool_feature into develop, our Azure Devops will automatically run a pipeline for this PR.
My assumption is that the resulting artifacts contain both the feature/cool_feature and the current state of develop. Is this correct?
I've looked at several pages, but I cannot seem to find a definitive answer:
- https://learn.microsoft.com/en-us/azure/devops/repos/git/pull-requests?view=azure-devops&tabs=browser
- https://learn.microsoft.com/en-us/azure/devops/repos/git/about-pull-requests?view=azure-devops
- https://learn.microsoft.com/en-us/azure/devops/pipelines/release/deploy-pull-request-builds?view=azure-devops
The reason I'm doubting is because we're reviewing our test strategy for this project. When determining if we should test the both the PR build and the build of develop after the PR is completed, we got into a discussion on the likelihood that the PR build is different than the "after-merge" develop build (both use the same pipeline). Also considering if we should make a merge of target branch (develop in my example) into the source branch (feature/cool_feature) mandatory before completing the PR. Azure does not seem to enforce this, it just checks for merge conflicts.
EDIT
I did find this question: https://developercommunity.visualstudio.com/t/pr-build-fails-but-branch-build-succeeds/1194209
This seems to confirm my assumption.
答案1
得分: 0
我认为“PR Artifact”不是一个正确的术语。应该是“Build Artifact”。“PR Artifact”是您的拉取请求构建的结果，其中包含了“feature/cool_feature”和当前开发状态。
> 我的假设是生成的构件包含了“feature/cool_feature”和当前develop分支的状态。这正确吗？
是的。DevOps通过内部合并分支将变更从“feature/cool_feature”合并到“develop”并进行构建。
> 我们讨论了PR构建与“合并后”develop构建在使用相同流水线的情况下可能不同的可能性。
它们应该是相等的。
英文:
I do not think PR Artifact is a correct terming. There is Build Artifact. PR Artifact is Build Artifact resulting of your pull request build.
> My assumption is that the resulting artifacts contain both the
> feature/cool_feature and the current state of develop. Is this
> correct?
Yes. DevOps merges changes from feature/cool_feature to develop through internal merge branch and builds it.
> we got into a discussion on the likelihood that the PR build is
> different than the "after-merge" develop build (both use the same
> pipeline)
They should be equal.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论