Tag Info

New answers tagged

2

I would much rather have a workflow where people clone the repository, create their own branch, make changes and commit them Absolutely they should - in my mind this is the reason for a distributed version control. If they lack confidence in the tools, a little practice should take care of that. We're working with one branch I'm sure this is a ...


0

I've decided the best way to do this will be to delete the config file from the websites config folder. I will then create a different config file for each environment which will be stored in puppet. Puppet can then add the correct config file into the websites config folder on provision depending on which environment it is running on.


0

You might want to look into tools like chef or puppet, as they are built for this kind of thing (provisioning). I know chef uses templates and variables in the script to substitute these. If a framework like this is unwanted you could always use a similar substitution on deploy scheme of your own or alternately expect configuration to be statically located ...


1

Should unit tests run on every git branch? This one is an easy one. The main point of doing continuous integration is to detect errors as early as possible in the build process. From this it should be clear, that you should a) run a testsuite on every branch of your code b) do not allow checking in code, which neither runs nor passes all tests ...


3

Run your unit tests on every branch. How do you know your code is actually working as expected otherwise? This goes the same for any other tests you may have. You say it yourself right here, "If they only run on the develop branch and a feature branch going on for long, I am afraid that the developer is pushing changes to his feature branch which would ...



Top 50 recent answers are included