“Let’s deploy, we’ll think about that on Monday”, is the Aggile Giggi‘s catchphrase, the italian funny parody of a rough developer on twitter. Actually, we all risk to be Agile Giggi when we release in production if we don’t have tools and processes to make the deployment as safe as possible. Let’s talk about testing. The risks associated with deployment can’t be reset but they can be reduced as much as possible by introducing automated tests into the workflow.
After a first thrilling edition here the second one is ended in no time. On the 9th and the 10th June took place the Mage Titans Italy. Never change a winner team and again this year, Bitbull in partnership with Space 48 arranged the event at the MotorK space. Demand to have the last year’s achievement was a too ambitious objective, but I believe we went far above of the expectations.
The versioning control systems let you keep track of any changes made over time and to cooperate more efficiently within teams of many people, in particular if, as in Bitbull, work remotely. We will not go into the explanation of what a version control system is, but rather we will see how to better manage the development flow with Git, the distributed version control software. Typically a repository is divided into two branches, master and develop, where master is the main branch which the code of the production’s version project resides in, while develop is the version with the latest developments that are about to be published and it is usually the active branch in test environment (from now on “staging”).