for a team of 12 developers, can you help me determine the process and workflow for creating and deploying the product using Mercury for version control and the city team for the build server?
We have a system that tracks problems and requests for promotion. most of them are rather minor bugs and improvements that one developer worked on in the timeframe of a day or two a week. I want businessmen and IT management to discuss priorities for tickets that developers work on. upon completion, these changes are committed and posted to the central repository and marked as dev in the ticketing system. qa and business teams should be able to select from tickets that are marked as dev complete and include those included in our product for the next version based on the priorities, qa and qa quantity of the avaialbility resource.
I initially thought that I could achieve this by forcing developers to commit changes to the new named branch for each ticket. in this case, the branch for each selected ticket can be combined by default, and the assembly and deployment on qa (and, ultimately, production) can be performed.
the problem with this is continuous integration. I think I can only configure teamcity statically to build a separate branch in our central repository. perhaps this is a limitation of the teamcity version we are in. 5.0.3 is currently in use, but updating is an option (and something we are likely to do anyway). maybe there’s some kind of complicated way to get it to assemble the tip and, therefore, the head of the branch on which the commit occurred, initiating the assembly? if developers commit and click on different branches for everything, and these branches do not merge with default until some time later it is late enough that qa now expects these changes to be built, and if there is a broken assembly, the cost is higher - there is no specific branchon which we need to build continuous integration.
, / - . . , , ?