[Buildbot-devel] ccache and buildbot (was Re: Buildbot 1.0: The Shimmering Vision)

[Bailey, Darragh]

> -----Original Message-----
> From: Charles Lepple [mailto:clepple at gmail.com]
> Sent: 20 August 2008 18:34
> To: Bailey, Darragh
> Cc: buildbot
> Subject: Re: [Buildbot-devel] ccache and buildbot (was Re: Buildbot 1.0:
> The Shimmering Vision)
<snip>

> > I wouldn't worry about trying to integrate ccache into buildbot, just
> set it up on the slaves to be available so that it's available to use for
> the buildbot user.
>
> Oh, I'm definitely not proposing ccache integration with buildbot
> upstream, just with the build configuration in master.cfg. I just
> couldn't get ccache to work as well as I could on the command line
> because of the $PATH issue.
>
> - Charles Lepple

That's what I'm suggesting you avoid doing, if you add the necessary files under /etc/profile.d/, the path will be set correctly. Provided you then re-login as the user you intend on running the buildbot slave as, and restart buildbot it will get propagated into all the builds run on that buildslave.

The following line always appears in the stdio file from each buildstep in my buildbot setup:
PATH=/usr/kerberos/bin:/usr/lib64/ccache/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin

But my master.cfg has no knowledge of the existence of ccache, its setup client side only.

Btw, if you use the sample makefile, it might be worth adding the following into it:
CCACHE_DIR := $(CURDIR)/ccache
export CCACHE_DIR

This ensures that the ccache dir used is kept within the buildbot area that does the build.

Very useful if the users home directories are not on the same filesystem as where the buildbot slave is running under.

--
Regards,
Darragh Bailey

Systems Software Engineer
Hewlett Packard Galway Ltd.
+353 91 75-4674

Postal Address:    Hewlett Packard Galway Limited, Ballybrit Business Park, Galway
Registered Office: Hewlett Packard Galway Limited, 63-74 Sir John Rogerson's Quay Dublin 2
Registered Number: 361933

_______________________________________________
The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error you should delete it from your system immediately and advise the sender.
To any recipient of this message within HP, unless otherwise stated you should consider this message and attachments as "HP CONFIDENTIAL".