Implementing Continuous Integration with a volatile hierarchy of library dependencies
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.
GitFlow with TFS 2013, bumping versions
We have TFS 2013 only for version control, Team City for building, a Nuget server and Visual Studio 2013. Little late in the game but we haven’t set guidelines for getting code from development into a build and package management process. Git-Flow as shown below will work for most of our projects (i.e. we need only one development line). We aren’t forced into TFS but I would like to see if GitFlow can work even with TFS (note: not much prior experience with TFS instead Git). With TFS 2013+ merging a branch like release below should be possible into master? There was a restriction (I think) with pre-2013 TFS that branch merging was only possible back to it’s origin (i.e. development in the release case).
GitFlow with TFS 2013, bumping versions
We have TFS 2013 only for version control, Team City for building, a Nuget server and Visual Studio 2013. Little late in the game but we haven’t set guidelines for getting code from development into a build and package management process. Git-Flow as shown below will work for most of our projects (i.e. we need only one development line). We aren’t forced into TFS but I would like to see if GitFlow can work even with TFS (note: not much prior experience with TFS instead Git). With TFS 2013+ merging a branch like release below should be possible into master? There was a restriction (I think) with pre-2013 TFS that branch merging was only possible back to it’s origin (i.e. development in the release case).
GitFlow with TFS 2013, bumping versions
We have TFS 2013 only for version control, Team City for building, a Nuget server and Visual Studio 2013. Little late in the game but we haven’t set guidelines for getting code from development into a build and package management process. Git-Flow as shown below will work for most of our projects (i.e. we need only one development line). We aren’t forced into TFS but I would like to see if GitFlow can work even with TFS (note: not much prior experience with TFS instead Git). With TFS 2013+ merging a branch like release below should be possible into master? There was a restriction (I think) with pre-2013 TFS that branch merging was only possible back to it’s origin (i.e. development in the release case).
SOA: Make each level of a service stack a package (NuGet etc.)?
Say I have a service that has the following hierarchy:
Starting to use TFS – handling internal dependant libraries – local nuget?
Approach 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 […]
Starting to use TFS – handling internal dependant libraries – local nuget?
Approach 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 […]
Starting to use TFS – handling internal dependant libraries – local nuget?
Approach 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 […]
Starting to use TFS – handling internal dependant libraries – local nuget?
Approach 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 […]
Best practices in managing nuget repositories [closed]
Closed 9 years ago.