Cruise API with authentication

Follow

Comments

5 comments

  • Avatar
    Jez Humble

    Your security configuration is a bit mangled – perhaps Beast isn’t parsing it properly.


    I haven’t used the NAnt get task’s authentication, but we have successfully used curl. Examples are here: http://studios.thoughtworks.com/cruise-continuous-integration/1.1/help/Artifacts_API.html


    Thanks,


    Jez.

  • Avatar
    andyd

    Quite right, Jez.


    Beast made a right mess of the XML I tried to show you.


    I have managed to get the LDAP right. I think the main problem was an incomplete config. I was changing the config for security without bouncing the Cruise Server between changes. I thought that the changes were being picked up, because a couple of times, the error changed after the config changed.


    It seems, though, that the full configuration was not being refreshed. Bouncing the service between changes soon helped to establish the correct errors, which soon helped to establish the correct configuration. Just mentioning it for others who might be changing config on the fly.


    I have also changed to use curl rather than that NAnt get, and that seems to be more successful than the wget or NAnt Get.


    Thanks again,


    Andy D.

  • Avatar
    Jez Humble

    Hey Andy


    Glad you got things working. Cruise Server should not need bouncing between configuration changes – if it isn’t, that’s a bug. I’ll make a note.


    Thanks,


    Jez.

  • Avatar
    thekua

    We also successfully used wget (using—user and—password options). Be warned not to use the—httpuser and the—httppassword options

  • Avatar
    thekua

    Although we couldn’t’ get wget working from a mac (though might be a bug with wget moreso). Specific version on the mac was GNU Wget 1.11.4.

Please sign in to leave a comment.