Hippo.NET feedback requested!

The Hippo.NET build tool is available quite some time. I've got some feedback (not very much) and there are some problem reports, mostly due to the rather limited installation manual.

Now the time has come to release a new Hippo.NET version, but I need some more feedback of everybody who is using Hippo.NET. So if you have tried Hippo.NET and you don't like, or you really like it, you have some problems with it, you know some cool features you would like to see, ... please give me some feedback. You can comment on this post or send me an email. THANKS!!

For those who never heard of Hippo.NET:
Hippo.NET is a tool for streamlining the build process of .NET projects in a team envirionment. It provides continuous integration by monitoring the shared Visual SourceSafe database and starting the build process when changes are detected. An important design goal is to provide a nice and easy-to-use user interface, to monitor builds and trigger the build process when needed. You can find some more information and screenshots on the website.

14 Comments

  • Jan,


    This sounds like an interesting little project. Any plans for NAnt support?

  • After running the installutil on the server it still didn't show up in the Services list.





    Can't the server just run as a normal program as well. It's kinda lame that I have to jump thru so many hoops just to try it out.

  • Personnaly I think a service is the correct way to run the server. If the install and the uninstall work, there should not be any hoops just to try it out.





    Y

  • It would be nice to have:


    1. the build requester in the build loggings. (windows account on client?)


    2. A possibility to copy the directory with the dll's from the server to the clients from within Hippo.


    3. Does the path has to be set on the server. This requires rebooting of the server. (for the system account in the service to get it) Can it be done in the config file?


    4. some errors result in a crash of the client programm. (servfer down)


    5. The error you get when the path to nant isnt set on the server could be better.





    Thanks.

  • Request:


    It would be nice if you could update the server code from the client without requesting a build. (You also can do a "get latest version" on the server, but there are no working folders set.)


    Automatically creating a buildfile for the project and the possibility to manage the main buildfile (add project, move project in buildsequence, comment project, ...) would be nice options.





    Very minor issues:


    If you start the Hippo client with a shortcut, and the windowstate is minimized, you regulary get errormessages but everything works.


    The Hippo buildfile builder (beta version!) always sets references to c:\Windows somtimes this is winnt. I do not think this can be changed in the website. But who knows, maybe sometimes in the client?

  • The download for 1.2.0 of hippo.net doesn't contain a hippo.server.exe.config file. Is there one available somewhere else?





    Thanks,


    Eric

  • I extracted the files to C:\Hippo, went to C:\Hippo\Server and typed: installutil hippo.server.exe





    and got the following error:





    C:\Hippo\Server>installutil Hippo.Server.exe


    Error dispatching command/test named 'Hippo.Server.exe'





    Here is the list of valid command/test/option names:


    +-------------------------------------------------


    | registerdatapath


    | registersqlanywherepath


    | registersqlanywherebinpath


    | getdatapath


    | getsqlanywherepath


    | getsqlanywherebinpath


    | registersqlanywhereodbcdriver


    | registeroracleoptions


    | getoracleoptions


    | validateschemarepovendorinfo


    | validateuservendorinfo


    | validatedbisempty


    | describelastinstalledschemarepo


    | initemptyschemarepo


    | relocateschemarepo


    | relocateuserdb


    | convertuserdb


    | convertschemarepo


    | copyuserdb


    | copyschemarepo


    | clientregisterschemarepo


    | registerschemarepofromfile


    | adddbset


    | dropdbset


    | renamedbset


    | copydbset


    | disconnectuserdb


    | reconnectuserdb


    | exportschemarepo


    | exportoldschemarepo


    | importschemarepo


    | exportschemafromuserdb


    | upgradeschemareposystemversion


    | upgradeuserdbsystemversion


    | unlockschemarepo


    | unlockuserdb


    | catchuptestdbs


    | cloneschema


    | deleteschema


    | purgedeleteduserdb


    | restoreuserdbschema


    | clearstatemachine


    | setschemarestriction


    | setrecursionlimit


    | dropchoicelist


    | checkin


    | uncheckout


    +-------------------------------------------------





    I'm guessing this is because the download doesn't include a hippo.exe.config file.

  • When will the buildfile generator be implemented in Hippo? I would like to try to push my company to using this, but since our project files change frequently, it is not an option to update the buildfile using the leadit website. If it's not going to be included anytime soon, is there a command line generator or are the classes available in cvs to do this?

  • Is there a .Net1.0 build of HippNet?

  • vb project file has ..\WINNT in the path. Visual studio translates this when different users open the project (i.e. WinXP , Win2k). The buildfile generator uses the ..\WINNT verbatim, instead of checking if it shouls use ..\Winnt or ..\Windows. maybe should use the System.Environment Static properties?

  • The service had problems accessing a VSS store on a network drive. I had to download the source and copy the code from the service into a form. Once it was running under my username it worked fine.



    If you have more than one project defined, you should be able to view them all from one client, instead of having to change the Hippo.Client.exe.config file to point to a different project name every time.



    You should also be able to change the configuration from the client (change the VSS path, username, client directory, etc.)

  • Agree with Adam,

    It would be really useful if more than one project can run in the client without having to change the config file.

    Have you any planst to implement this?

    Bert-Jan

  • Correction. My last post should say Draco.NET, not Drago.NET

  • Lucy! Please call me,Lucy! Please call me

Comments have been disabled for this content.