CodingGorilla Posted December 22, 2011 Report Share Posted December 22, 2011 It was on the download page, I think maybe they pulled it because the "cm log" function is broken, and the teamcity plugin relies on that command, so the teamcity plugin doesn't work either. Link to comment Share on other sites More sharing options...
manu Posted December 23, 2011 Report Share Posted December 23, 2011 Yep, we are working on the "cm log" command, actually we are not fixing it, we are rewriting it. I think it will be ready today, but we have to make a new release to hold the change. Link to comment Share on other sites More sharing options...
ryexley Posted December 23, 2011 Report Share Posted December 23, 2011 Is this the PlasticSCM v4 version of the plugin that you're rewriting? If I have a copy (a co-worker had previously downloaded it...I didn't know we had it) of the older version for PlasticSCM v3 does that still work? Unfortunately, we're on v3 and can't upgrade because...well...you know why. So does the v3 version of the plugin work? Link to comment Share on other sites More sharing options...
manu Posted December 23, 2011 Report Share Posted December 23, 2011 Hi ryexley! Yes the v3 should be working on PlasticSCM 3.0. Link to comment Share on other sites More sharing options...
ryexley Posted December 23, 2011 Report Share Posted December 23, 2011 Now that I'm neck deep into a configuration for the v3 plugin, I'm finding something missing from the plugin that I'd love to see built-in to the v4 plugin...hopefully before its too late. I noticed that there doesn't appear to be a way, in the VCS client configuration for Plastic SCM in TeamCity, to specify a specific user and password to use when connecting to Plastic SCM. It would be REALLY nice to be able to specify a user and password to use to connect to Plastic without requiring/assuming that it connect with the user that the TeamCity service is running under. Can we make this happen? Link to comment Share on other sites More sharing options...
CodingGorilla Posted December 23, 2011 Report Share Posted December 23, 2011 I'm not sure about the 3.0 version, but the 4.0 version relies on the client.conf file, which is created when you install the client and or run the client configuration utility. It actually has nothing to do with TeamCity (correct me if I'm wrong). Link to comment Share on other sites More sharing options...
ryexley Posted December 23, 2011 Report Share Posted December 23, 2011 That may be the case, I'm not sure. Either way, it would still be nice to be able to explicitly specify a username and password to use, regardless of the credentials of the process making the call (TeamCity). I was even noticing that the command line client doesn't appear to provide any means (that I was able to see anyway) of specifying alternate credentials for execution of commands. That would REALLY simplify third party integrations. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.