We have a CI build set to trigger on changes to a specific repository.
When a change is triggered we pull from 2 repos to do a build, the repo that changed and a repo that stores our build scripts.
In the list of changes, we get the changes from the triggered repo as well as the build scripts repo which last had changes weeks ago and has had several builds against it succeed.
Is there a way to suppress the changes from that other repo or when should those changes finally fall off?
Hi Jeremy
Both the Code Changes area on the Details tab of Build view and the Changes tab of the Build view always show the latest revision or changeset for each repository. The idea is that you can see which set of files were available to be used in the workspace of each build. Perhaps we should have labelled this as Revisions rather than Changes? Note that the changeset which triggered the build is marked with a star.
The only way to stop the latest changeset appearing in these view is by removing the association of the repository with your configuration in the repositories tab of the configuration wizard or by disabling the repository.