Recently my company setup a build server using Bamboo and a private Nuget Feed which is populated by the successful builds being deployed from the build server.
There is a hierarchy of projects under heavy development setup for use in bamboo with a fairly simple, linear dependency graph. Before being setup on bamboo all devs had to clone the repository being worked on and all of its dependencies and make a new branch in each project. As almost all changes at this point are breaking changes, this was a bit of headache.
So now with the new tool of Bamboo in the mix, as a dev, what would my workflow look like if I needed to make some changes in Project A that will also require changes in Project C where Project B and C is dependent on A and C is also dependent on B.
A | | | B | | C
I want to make certain all tests still pass in Project B after my changes to project A before moving on to make the changes in Project C. Are there any resources that help explain what developers workflow should be at this point? It seems he can either pull down, setup the dependencies manually and test B. Or he can setup special builds on Bamboo to handle the this intermediate state of the projects and then download the resulting nuget packages. I feel uneasy with that solution because it requires a deeper understanding by the devs of Bamboo and the build server (And I don't understand it all well at this point, to explain it all to them).
This problem compounds the more dependencies there become on a lower level library. Are there any resources that explain the accepted approach to this problem?