Release services with DVCS Mercurial
Nike magista shop my team of developers is migrating from SVN to Mercurial. Having researched DVCS recommendations, Is probably the best suggested that we develop against feature branches of the repo mainline, Test them as a stand alone, Then nike magista sale cherrypick the characteristics we want in each release, Before merging those selected branches into the mainline and finally releasing it.
Mystery: What I’m looking for is tips for some sort of software tool that will make my role of”Tools release manager” Tricky, In that it’s going to allow me to control(Cherrypick) Which divisions(Highlights, Bug solutions, And also so on) Are joined(The usage of Git, And even Mercurial) Into which computer programs releases(In each local climate), nike magista sale And be capable of producing the binary deployment artefact.
BuildMaster, By Inedo This was the nearest match, Without a doubt, But was not quite suitable due to its lack of VCS branch picking/merging purpose. I would say however that this is a very nice software system, And would suggest it, If they can fit your usecase, And is properly priced, Even for institution use.
Am currently evaluating as follows tools:Bitbucket Feature Branch oversight(Since we use Bitbucket for our works, Seems prudent to gauge their approach)
Since DVCS is interested in us, These things had been dismissed prematurely, So go ahead and reeducate me.
This may not be as automated as your want but TortoiseHG allow you to select what branch you want to merge and indicate that the branch is merged. The downside is that I do not think there nike magista shop is a TortoiseHG mode which you could see what branches are still unmerged.
I’m tinkering with the revision set filter in TortoiseHG to see if you can duplicate the result from within THG but no luck yet:(
The issue I see here is more of a source management one what you need to do is add a concept of a release branch which is where you can cherry pick feature branches to integrate and test. Any other tool you want to use can then be pointed at said release branch with no need a whole lot off offline work.
Another variation on this idea would be to use a fork and pull requests to pull this stuff into a clean”Production” Database for each release. I can’t claim to did this this way though.
While I can see how you develop your workflow for release(Is it tag in arrears branch or special separate branchperrelease) And topology of your archive(Does later launches inherit all features from previous emits or not), I’ll try only a certain amount of iterations:
As as nike magista sale of now noted, In my opinion, TortoiseHG will probably be good main tool
If previouslymerged features grew up honing in later releases and naming of branches follow and all branches are open(Differ only by the infection”Already merged or not”) And releases nike magista shop are tags you can use in TortoiseHG these types of revsets nike magista shop in filter(But for building up lists CLI is better, From my POV revset with templates deliver nice output) nike magista shop.