RE: CruiseControl.NET integration?

Yea, I am withdrawing that recommendation.  It was based solely on my desire
to not burden Draco.NET with an API file.  It does all of it's current SCCS
support in a fairly lightweight manner.  I'm not particularly certain that
the official project will accept the addition of the API.  (Which is what
I've been shooting for; a version of integration built into Draco.NET and
not available separately.)

Instead I've got a custom command line client that does GET and HISTORY and
uses the API, it can be recompiled against new versions of Vault until the
official command line client can produce XML that won't cause Visual Studio
to choke up blood and allow for a date limited history command.  Yea, it's
extra baggage but it's extra baggage that will hopefully get thrown away in
the future and doesn't HAVE to be included with Draco.NET.

It's my opinion that if you want to tango with the web service you should
just hop out and write an entire SCCS product - that's where you're going.
I wouldn't want to tackle some of the issues involved if I was getting PAID
to do so, much less on my spare time. :)  As for sanity... Whoever said we
were sane to begin with?

To defend Jim's sanity I DID say that the web service was my ideal method of
working with Vault in terms of Draco.  I worked on it for two weeks and got
nowhere.  

And Eric, I felt that article was aimed squarely at me. ;p

Brian Schkerke
Lead Developer
NETCO, Inc.
http://www.netcotitle.com
(636) 925 8657

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Eric Sink
> Sent: Monday, February 23, 2004 1:53 PM
> To: [email protected]
> Subject: RE: [vault-list] CruiseControl.NET integration?
> 
>  
> > Ideally, per Brian Schkerke's recommendation, it should 
> just use the 
> > webservice for all transactions.
> 
> <imitate voice="Lumbergh">
> 
> Mmmmm, yeah, I'm going have to go ahead and sort of disagree 
> with you on that.
> 
> </imitate>
> 
> Seriously, nobody should be calling the web service API 
> directly.  That's what the Vault Client API is for.  Calling 
> the Web Service will threaten your sanity.  See below for 
> more details:
> 
> http://support.sourcegear.com/viewtopic.php?t=237
> 
> --
> Eric Sink
> Software Craftsman
> http://software.ericsink.com/
> 
> 
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of 
> James Geurts
> Sent: Monday, February 23, 2004 1:32 PM
> To: 'Kirk Marple'; [email protected]
> Subject: RE: [vault-list] CruiseControl.NET integration?
> 
> Hi Kirk,
> 
>  
> 
> I hacked together Vault support with Draco.Net.  I say "hack" 
> as it uses the vault libraries for interaction with Vault 
> server.  Ideally, per Brian Schkerke's recommendation, it 
> should just use the webservice for all transactions.  I plan 
> on looking at/helping Brian with the webservice solution when 
> I get finished with my current project.  In the mean time, if 
> you would be interested in the files that I use currently, I 
> can provide those.
> 
>  
> 
> Jim
> 
>  
> 
> ________________________________
> 
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Kirk Marple
> Sent: Monday, February 23, 2004 2:17 PM
> To: [email protected]
> Subject: [vault-list] CruiseControl.NET integration?
> 
>  
> 
> I'm looking into continuous integration servers like 
> CruiseControl.NET.
> 
>  
> 
> It currently has support for CVS, PVCS and Subversion.
> 
>  
> 
> Has anyone hacked together the configuration for Vault, by 
> chance?  I didn't want to reinvent the wheel if possible.
> 
>  
> 
> Thanks,
> 
> Kirk
> 
>  
> 
> -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
> 
> Kirk Marple
> CTO/VP of Engineering
> Agnostic Media, Inc.
> e: [email protected]
> w: www.agnostic-media.com
> 
> blog: www.1968.org <http://www.1968.org/>  
> 
> You can get my Digital ID here:
> https://digitalid.verisign.com/services/client/index.html
> <https://digitalid.verisign.com/services/client/index.html> 
> 
>  
> 
> 
> _______________________________________________
> vault-list mailing list
> [email protected]
> http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list