I'm trying to get up and running with TFS 2013. This is my priority order for implementing it.
- Start using it for existing Git Repo projects.
- Then get automated builds working from check ins (CI?)
- Start to use for Work Items and backlog etc, when more comfortable with it.
Is that a good phased approach, so that we aren't trying to build Rome in a day?
After setting up a repository for our first solution in it, I got the team and git version control etc setup up. The difficulty came when I tried to do a build, but had dependant library issues.
My initial research suggested that creating a local nuget share/server was a good way to tackle this. So I created a separate repository in TFS for the shared library, it has no other dependencies, so a default build worked fine.
I assume then the intention is to get the build definition to automatically create a nuget package and dropped into the appropriate nuget share. Then that nuget package is now used for functionality in the first original project, rather than a project reference to the shared library?
Then when the first original project is checked in, and a build triggered, that build can use the local nuget share for its dependency (somehow!)?
Is this the best way to tackle this?