Instead, let’s create a new branch where all additional changes will be committed. The following script is used to make a change:Īssuming that after committing a change related to the Address table a database reached a point where it can be promoted to other environments, we do not want to break this by commit each and every new change to the trunk project.
We’ll made additional change that will be committed to the trunk project before creating a new branch. In order to do so, the trunk folder will be set as a project in the last step of the Source control wizard:Īfter a database is linked, let’s initially commit all objects to the previously selected trunk project: We’ll link a database to a Subversion repository, specifically to the trunk folder. It is important to mention that for the purpose of this article, we’ll use a Subversion repository that has the following structure:
#VISUALSVN EXPORT REPOSITORY HOW TO#
To find out how to link a database to a Subversion repository, check the article: How to link a SQL Server database to a Subversion repository. We’ll use a Subversion repository hosted locally by Visual SVN Server but all the entire workflow goes the same way regardless of the used Subversion repository. In order to make a new branch active and to be able to commit changes, a database must be re-linked.Īs the final part, we’ll merge changes committed to a new branch with the main branch. Next, we’ll create a new branch from trunk.
The branches folder will keep all the branches created along the way while the tags folder contains all tags aka labels created. The trunk folder is a main line that should contain only tested changes that are ready to be promoted to other environments. The default folder structure in Subversion means a single-project repository exists with top level folders: trunk, branches and tags.
0 kommentar(er)
