0

I am wondering why my build pipeline for Azure DevOps is getting practically all the changes instead of just the most recent one?

The previous WI and detected changes

I only made one change to 1 file, that didn't have an associated work item. This is what the change looks like. As you can see I have only changed one file. So why is it detecting all the changes?

enter image description here

I thought maybe it was because I didn't have this option enabled. enter image description here

But even with that option enabled on a pipeline setup the EXACT same way all the changes are still pulled. Am I missing something subtle here?

deathcat05
  • 429
  • 1
  • 5
  • 18

2 Answers2

1

There's an option on the pipeline to automatically link work items that are completed in a run.

You can edit the Pipeline and in the settings, tick Automatically link work items included in this run. You can pick * for all branches, or a specific branch.

Setting the automatic link work item option

Jake Edwards
  • 1,190
  • 11
  • 24
0

Not sure what you did for your pipeline. Every time you change the files of repos for pipeline and then re-run the pipeline, it lists the changes for each build for the current project. This depends on how many changes you have made to the repo project since the last pipeline.

The below shows:

enter image description here

Then, click into the latest pipeline, and that is true, it will list all changes compared to the previous pipeline.

enter image description here

Click into it and you could get the detailed every single change.

Mr Qian
  • 21,064
  • 1
  • 31
  • 41
  • I used the classic editor to create the pipeline, and I have a CI trigger that happens everytime a push is done to a stage branch. This was the first time the pipeline had ever been run. Does that have anything to do with it? Also, when I go to click on the pipeline run it shows the 172 changes and 24 linked Work Items... – deathcat05 Jun 10 '21 at 15:06