DVCS with Central Build/ automatic push to server feature?

 

I am looking for alternatives to NWDI (Stands for Netweaver Development Infrastructure by SAP) source control system for developing Java EE Applications. Primarily because:

  • NWDI is not DVCS : So developers have to be online to do just about anything.
  • User Interface: Its very difficult to use and train developers on using this system.
  • Tracking Changes/Generating Reports: Very limited support for this. For example I cant find out what projects (Files within the project) have been changed in the last 2 weeks.
  • Code Review: You can do code reviews, it has a good diff utility. But thats about it, there is no way to attach code reviews to a change request.
  • Branching and Merging are extremely painful.

    • However the current system has a few handy features:

  • Automatic Builds: No need to write any build scripts , everything is built in. So when a new repository (we call it track) is created it automatically configures the build based on the type of components (Supported by the repository) selected on creation. A Central Build is triggered whenever a developer commits (Activates the changes). Irrespective of the status of the build the changes are now inflicted on the entire team.

  • Automatic push to Central Test Server: While creating a repository you can define all the servers (Central test, QA, Prod). A developer can push his changes by a click of a button to Central Test Server. Again everything is built in and there is no need to extend any hooks like you have to do in Mercurial.

    • I was exploring Mercurial, Kiln and but couldn't find anything helpful. For mercurial Hooks can be used to do the same but I guess some customization effort is required.

    Are there any cool DVCS like Mercurial which does the above 2 as well or is it something that I have to customize to make it work?

    I don't know of a DVCS proposing everything build-in.
    The only alternative (not DVCS, but with some of DVCS characteristics in it) is Rational Team Concert or RTC (free for up to 10 developers).

    With a DVCS alone, the usual setup for CI and reviews is:

  • Git
  • Gerrit (review)
  • Jenkins (scheduler)

    • See "Using Gerrit Git Review with Jenkins CI Server"

    Looks like there nothing useful out of the box. I am going to try out Kiln as it appears to be easy to use and try customizing it.

    链接地址: http://www.djcxy.com/p/23278.html

    上一篇: 大中型开发团队如何不断推动对DVCS的改变？

    下一篇: 具有中央生成/自动推送到服务器功能的DVCS？