[Buildbot-devel] Buildbot and Perforce
tony.walker at crocodile-clips.com
Wed Jun 1 09:16:24 UTC 2005
Absolutely peachy, I think the initial 'starting p4 sync' threw me. I
altered the permissions on the 'full', 'build' and 'source' directories
of the buildbot slave even though the slave is running with the correct
account. I should have spotted that one....!
I had noticed that when it had attempted to run it the first time around
(a while ago now), the permissions set on the 'full' directory were set
to 700 so I'm not sure what the issue was there. However, a quick write
by all change has fixed it's wagon, I now get a complete sync with a
full log and exit code 0!
Nice one Brian! Here's to happy building!
> -----Original Message-----
> From: Brian Warner [mailto:warner-buildbot at lothar.com]
> Sent: 01 June 2005 09:45
> To: tony.walker at crocodile-clips.com
> Cc: buildbot-devel at lists.sourceforge.net
> Subject: Re: [Buildbot-devel] Buildbot and Perforce
> > starting p4 sync
> > rm -rf /home/developer/Buildbot_Slave/full/build
> > in dir /home/developer/Buildbot_Slave/full (timeout 1200 secs)
> > argv: ['rm', '-rf', '/home/developer/Buildbot_Slave/full/build']
> > program finished with exit code -1
> That looks like it's the 'rm -rf' command that's failing, and that it
> even getting to the phase where it runs p4. Is there any chance that
> directory is owned by someone other than the user running the
> Permissions problems? (the 'build' directory won't exist the first
> gets run.. the '-f' flag should make sure that this isn't a problem).
> The usual sequence should be:
> rm -rf .../build
> p4 sync (in .../source)
> cp -r .../source .../build
> > Is this a typical 'buildbot' log output or do I have to switch on a
> > flag to get more info?
> Yup, this is as much information as you can get. The blue lines are
> "headers", produced by the build slave to describe the command it is
> while the rest are coming from the command itself (both stdout and
More information about the devel