I created a cvs checkout action tonight in one of my finalbuilder 5 projects and checked it in. Then a co-worker checked out that finalbuilder project and tried to run it. It failed over and over with bad username password. We spent pretty much the entire evening tyring to figure out why it was working on my computer and not his. We finally figured out that I had tested the cvs creds manually before I setup the finalbuidler action. And finalbuilder wasn't overriding those creds. So when he tried to use it on his machine without having ever tried to use that new cvs user, it failed.
So why isn't finalbuilder overriding the cvs credentials? I'm using tortoisecvs as my cvs and we are using sspi for login. I put the credentials in with the actual action (NOT the tools/options cvs default).
I have just been doing some reading and I believe it should work. If you are using tortoisecvs you will need to set the CVS version to CVSNT. The only real difference this makes is where FinalBuilder stores the password from the login action. CVS uses a file in the users home directory, CVSNT stores passwords in the registry. I don’t have a cvsnt server setup at the moment, if the above info doesn’t help then contact support to open a support case and we will get it sorted out.
nope. This doesn’t work. Putting the username and pass in does absolutely nothing. Can we get this debugged? We need to be able to have finalbuilder use CVS with the correct username and password and not just try to use whatever is cached on the machine.
ok, this problem has cropped up again. I'm not sure why this has come up again but it's just not working.
No matter what I do, I can't get finalbuilder to login to CVS (even with the cvs login command). If I go and login with tortoisecvs and run a cvs update (or just about any command) and THEN run finalbuilder, everything works fine. But no matter how many times I run this locally, I can't get finalbuilder to login to cvs unless I"ve done it with some other tool first.
Some notes, we are using SSPI authentication and we have tripled checked that the password on both sides is correct.
I just want to thank the finalbuilder guys for working with me to figure out the problem. It turned out to be a really small bug in how the cvs command line is saved in finalbuidler. They fixed it and we are now good to go. Thanks again to the finalbuilder crew for being so dilligent on getting this fixed!