I know that there are already many questions on this topic, but I had problems finding exactly what I need.
We are a small development team that currently uses SVN, but will soon switch to Git. We are used to checking changes and insisting on the current website throughout the day, but currently do not have the formal testing procedures that we would like to add. The way I'm used to doing this with SVN is:
- develop in a personal test environment
- check your changes.
- send the current repository files to the global (production) test web server and test
- send current repository files to web servers
This, obviously, can create some problems, especially if the communication is not very good. I survived the times when unverified changes are a thing of the past and something that we would probably avoid.
What I present is the Git master repository, which stores the tested code that runs on live servers. Then you have a clone of this repository that is used for version checking. I would like to have a script that is responsible for pulling changes from the requesting developer, posting them in a branch in the test repository and running some automated tests to make sure that nothing significant is broken. When all this is checked, this branch can be combined and redirected to the main server and exit to the servers.
-. , . !
EDIT: , .