You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We facing an issue with this ado extension.
Let me summarize it.
Imagine that your CI CD pipeline is triggered for the commit xxx and between the moment you triggered the pipeline and the moment you checkout for building your stuffs, you pass a PR, it can be really inconsistent.
Imagine this change is spread all over the solution and you build muiltiple artifacts. Depending on the timing, you will have some artifacts that will take commit xxx because last during the run, and some will take commit yyy because last at this moment.
I think it can be really complicated to manage depending of your way of working but it could be good to have the possibility to give Build.SourceVersion and filter
Hello,
We facing an issue with this ado extension.
Let me summarize it.
Imagine that your CI CD pipeline is triggered for the commit xxx and between the moment you triggered the pipeline and the moment you checkout for building your stuffs, you pass a PR, it can be really inconsistent.
Imagine this change is spread all over the solution and you build muiltiple artifacts. Depending on the timing, you will have some artifacts that will take commit xxx because last during the run, and some will take commit yyy because last at this moment.
I think it can be really complicated to manage depending of your way of working but it could be good to have the possibility to give Build.SourceVersion and filter
This is working!
So like this, you are sure that the contract between the pipeline execution and the checkout process is consistent.
The text was updated successfully, but these errors were encountered: