Home

News: Parabuild 2.0, Released

  1. Parabuild 2.0, Released (13 messages)

    Viewtier Systems, Inc., has announced the release of its software build management server, Parabuild 2.0. Parabuild helps software organizations reduce high risks of failures of projects caused by broken code base by delivering uninterrupted daily builds. Parabuild is priced at $345 for a single-build configuration.

    Software build is a process of transforming of project source code into a working application. Broken builds cause delays and overspending that may increase risks of project failure. Parabuild attempts to cure the pain of broken code bases. With Parabuild, daily builds can succeed if the head of the code base is broken. Continuous integration builds provided by Parabuild ensure that new changes integrate into existing code base.

    Key Parabuild Features

     - Continuous integration builds.
     - Daily, nightly and QA builds.
     - High speed Web interface.
     - Integration with ClearCase, Perforce, Visual SourceSafe, Surround SCM, CVS and Subversion.
     - Build scripting: shell scripts, Perl, make, MSBuild, nmake, ANT, nANT, Maven, Jam and VB.
     - Multiple platform support: Windows, Cygwin, Linux, Solaris, HP UX and generic Unix, including Mac OS X.
     - Release notes from Bugzila, Peforce jobs and Jira.
     - Two-minutes installation; fifteen minutes to first build.

    Parabuild is Different

     - Uninterrupted daily builds.
     - Remote multiplatform builds.
     - Running existing build scripts.
     - Low to zero administration.
     - Searchable logs and results archive;
     - Group-based security;

    A working evaluation version of Parabuild 2.0 is available for download at http://www.viewtier.com/downloads/index.htm.

    Threaded Messages (13)

  2. Costly software[ Go to top ]

    Why should I use this when I can use CruiseControl?
  3. Well, look at the features. It offers more than what CruiseControl comes with.
    Ever checked out the latest Continuum release? That's a pre-pre-pre-Beta piece of software released way too early. Got me lots of headaches :-( OpenSource software like that motivates me to invest some money into professionally maintained software... :-)

    Regards, Rias A. Sherzad
    sherzad.com
  4. Cruise control[ Go to top ]

    I rather use luntbuild over cruise control, you should check it out!

    Anyway congrats on the release!
  5. About luntbuild...[ Go to top ]

    I rather use luntbuild over cruise control, you should check it out!Anyway congrats on the release!

    I'd like to share some of my personal experiences with luntbuild:

    I started with CruiseControl and when had plenty of reliability problems with it, went to luntbuild. After a couple of weeks of misery I moved back to CC, which had a new version available fixing the problems. I haven't since looked back.

    Luntbuild web UI is terrible and very unintuitive. I prefer the CC XML configs. Also, there was no way to customize the way the notification mails looked like in luntbuild. CC takes the points here too, as luntbuild mails are close to worthless... I really hope luntbuild has gotten better since 3 months ago! :)
  6. About luntbuild...[ Go to top ]

    Sorry to hear about that :/ My experience with luntbuild was so far better than with CC. I didn't had problems using it's UI, but it's just plain ugly, I wish it was more polished ;)
  7. About luntbuild...[ Go to top ]

    Have you checked out QuickBuild? It is professional version of Luntbuild. It is totally re-designed based on lessons from Luntbuild. The UI is now more professional, and you have the ability to customize notification email using Velocity, so that interesting part of build logs can be inserted in Email text, or sent as attachments.
    Regards.
    I rather use luntbuild over cruise control, you should check it out!Anyway congrats on the release!
    I'd like to share some of my personal experiences with luntbuild:I started with CruiseControl and when had plenty of reliability problems with it, went to luntbuild. After a couple of weeks of misery I moved back to CC, which had a new version available fixing the problems. I haven't since looked back.Luntbuild web UI is terrible and very unintuitive. I prefer the CC XML configs. Also, there was no way to customize the way the notification mails looked like in luntbuild. CC takes the points here too, as luntbuild mails are close to worthless... I really hope luntbuild has gotten better since 3 months ago! :)
  8. About luntbuild...[ Go to top ]

    I'd like to share some of my personal experiences with luntbuild:I started with CruiseControl and when had plenty of reliability problems with it, went to luntbuild. After a couple of weeks of misery I moved back to CC, which had a new version available fixing the problems. I haven't since looked back.Luntbuild web UI is terrible and very unintuitive.

    Kai, try Parabuild - we worked hard to make the UI easy to use and understand. And the installation takes only 2 minutes: http://www.viewtier.com/downloads.htm
  9. Costly software[ Go to top ]

    Why should I use this when I can use CruiseControl?

    You may want to use Parabuild because it just works. Try it for yourself: http://www.viewtier.com/downloads.htm
  10. Differant Approaches[ Go to top ]

    Why should I use this when I can use CruiseControl?

    You are really looking at significant differances in approach when you talk about more of a build management system versus cruise which is very focused on being a continuous integration system. Cruise does that job nicely and that focus gives way to billion notification mechanisms and features like really nice JUnit handling. CI and build management overlap in functionality but differences in emphasis are telling.

    What it doesn't do as nice of a job at doing is tracking your build history and giving you a finer level of control through the gui ui. I tend to view cruise as being a lot stronger at helping developers day to day than at helping to manage releases to production and such.

    Parabuild helps provide this support with some nice graphs for management and other controls that I'm sure Slava could talk about at length. The Anthills, LuntBuild, and I believe QuickBuild would also provide good support for things like dependency management and alternate build profiles for projects.

    If cruise meets your needs perfectly awesome. If you're looking for a system which focuses more on build management than on continous integration, consider looking elsewhere.
  11. Differant Approaches[ Go to top ]

    Eric,

    There is a great thing about cruisecontrol is that its freeness promotes introduction of continuous integration. Once the beachhead is there, organizations can use our ongoing promotion for those who want to switch from open source products to Parabuild and to start using a production-grade build system. Unlike other systems, Parabuild doesn't require CPR on an hourly basis. It just works...
  12. Differant Approaches[ Go to top ]

    You are really looking at significant differances in approach when you talk about more of a build management system versus cruise which is very focused on being a continuous integration system.

    Parabuild is a quality continuous integration system. We have customers who switched from CruiseControl to Parabuild just for this reason.
  13. Parabuild 2.0, Released[ Go to top ]

    Quick browse through Viewtier website reveals that Parabuild is the only product from the company founded in 2004. Also, 2.0 is in fact their first 'public' version, which looks like marketing trick for me (who will buy version 1.0 after all?)
    $345 doesn't look like an investment, but the immaturity of the vendor casts serious doubts. I would rather prefer to spend $1000 on build automation product from an established vendor like Atlassian on IntelliJ.

    Another point is flexibility. Just setting up continous build system for a straightforward build isn't rocket science, any decent Java developer is able to do this within 2 hours with opensource tools.
    But when things tend to get complicated I'd rather stay with opensource CruiseControl or LintBuild or DamageControl, so I can tweak and tailor it to custom needs, when I need non-trivial stuff, like multi-project multi-branch builds with interdependencies.
  14. Parabuild 2.0, Released[ Go to top ]

    Quick browse through Viewtier website reveals that Parabuild is the only product

    This is correct, we believe that being a single product company helps us stay focused and do what we do best, the build management software.
    from the company founded in 2004.

    2004 sounded good to the founder :)
    Also, 2.0 is in fact their first 'public' version, which looks like marketing trick for me (who will buy version 1.0 after all?)

    Versions prior to 2.0 were private and were available to consulting clients only. Parabuild 2.0 is the first public release.

    $345 doesn't look like an investment, but the immaturity of the vendor casts serious doubts.

    Parabuild is a mature product. Actual development started in 2000.
    I would rather prefer to spend $1000 on build automation product from an established vendor like Atlassian on IntelliJ. Another point is flexibility.

    This is the first time I hear that Atlassian or JetBrains produce build management software. But you are definitely in your right to buy from a vendor of your preference.
    Just setting up continuous build system for a straightforward build isn't rocket science, any decent Java developer is able to do this within 2 hours with open source tools. But when things tend to get complicated I'd rather stay with open source CruiseControl or LintBuild or DamageControl, so I can tweak and tailor it to custom needs, when I need non-trivial stuff, like multi-project multi-branch builds with interdependencies.

    We do not compete with open source tools as they tend to serve fixed cost organizations with no budget for software development tools.

    Parabuild is not a construction set that you may use to try to assemble something that might work if you have enough luck and persistence.

    Parabuild is a production-grade build management server that just works - out of the box.

    Regards,

    Slava Imeshev