[Buildbot-devel] perforce authentication not working

[Hari Kodungallur]

On Wed, Jul 2, 2008 at 11:04 AM, Henry <dimensiondude.oss at gmail.com> wrote:

> I hadn't, thanks. That works for P4Source, though I am still having a few
> issues with the builldslaves.
>
> That is better than a plain text password in many ways, except that it will
> not work across multiple machines (my buildmaster checking for changes and
> my buildslaves getting sources). Is there any way to not have to enter a
> separate ticket for each buildslave? Parsing one from ~/.p4tickets would be
> easy, except I don't know how to make it run on the slaves rather than the
> buildmaster.
>

"p4 login -a" will give you a ticket that is valid on all hosts.



>
> On Jul 1, 2008, at 5:50 PM, Hari Kodungallur wrote:
>
>
>
> On Tue, Jul 1, 2008 at 2:46 PM, Henry <dimensiondude.oss at gmail.com> wrote:
>
>> I am trying to use buildbot with a project that uses perforce for
>> version control, and it is failing at polling it for changes.
>> Specifically, it rejects the password as incorrect or missing. I can't
>> tell quite what is going on. If, at the command line, I put the
>> password into P4PASSWD or using it at the 'p4 login' prompt, it works.
>> But, if I put it after -P, it does not work.
>>
>> buildbot never works, where I 'p4 login' or 'export' the P4PASSWD
>> variable or pass P4Source p4passwd='thepassword'.
>>
>> Any ideas on why this is happening, or how I can debug it further?
>>
>> P4 poll failed: [Failure instance: Traceback (failure with no frames):
>> <type 'exceptions.IOError'>: got stderr: 'Perforce password (P4PASSWD)
>> invalid or unset.\n']
>>
>
>
> Have you tried giving the login ticket instead of plain text password to
> the p4passwd argument? (your login ticket should be in ~/.p4tickets file or
> you can get it using p4 login -p)
>
> rgds
> -Hari
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20080702/5bcb1ce0/attachment.html>