I am experimenting with using a private NuGet repository and jenkins to deal with dependencies.
Let's say we have exe A and libraries B,C and D.
Exe A depends on library B which depends on C and D.
On push of code changes to B,C or D jenkins builds and publishes a separate NuGet package for B,C and D to our private repository. All well and good.
I would like to be able to have any changes pushed to C trigger a nuget update and build of B and then A.
The problem is is that the nuget update causes edits of the packages.config file in the dependent project. This change happens in the jenkins workspace for that project.
This edit, in my mind, should be pushed to the SCM. Which would then cause a jenkins build ad infinitum.
A: Am I doing it right?
B: Is there a way for this to work?