This report is due to a configuration change made in our Perforce server. Maybe this is more of a wishlist.
We recently moved to using Perforce logins. That is, in order to use Perforce a user first runs "p4 login" and enters their password and then a ticket is stored allowing access for a period of time.
However, this breaks the Perforce triggers and Actions. I am not entirely sure that the Perforce triggers are storing and using the password that is set via the web interface. I am sure that sending a password to p4.exe causes problems via the -P option. I am sure that running "p4 login" (or the graphical client) and removing the P4PASSWD override in FinalBuilder 6.3.0.1712 and 6.3.0.1812 allow the ticket feature to work properly.
To work around this I created a project that simply runs p4 login every 1/2 ticket duration. However, this is less than ideal since the password is temporarily stored in a file and also stored either in the project or in the project configuration in a variable.
We are using Perforce server version : P4D/NTX64/2009.1/213171 (2009/09/02).
Ideally p4 would give an error message other than 1, which is the error code that was being returned. However, using p4 login in place of specifying a password would be better.
We’ve added support for Ticket-based authentication in Finalbuilder Server and are just working on the FinalBuilder actions, should have a new build out to you soon.
Here is the new build of FinalBuilder Server which adds the support for ticket based authentication to the Perforce trigger, we don’t yet have a new build of FinalBuilder as it’s requiring quite a bit work to the process execution code, but we’ll let you know when a build is available.
Paul - when do you expect a FinalBuilder Professional release that supports the ticket in Perforce? Secondly, your recommended workaround for the time being... do I chain the DOS command right behind the current Perforce action in the designer or do I need to substitute the current Perforce action for the workaround completely?