[Buildbot-devel] problem in triggering the builds

Brian Warner warner-buildbot at lothar.com
Tue Sep 27 23:03:16 UTC 2005

> From: "KR Arun. Chand" <achand_st at beceem.com>
> i ve bin facing a problem .i ve installed buildbot on our server ..
> but the build is bin triggered  only when i commit as a user called cvs.
> In my master.cfg i have given as 
> cvsroot=":pserver:cvs:abc123 at serverip:/cvs/repository"  .(cvs is a user)
> when the others commit  it throws up an error that reads fresher did not connect, and the build is not triggerd.i greped for the freshcvs daemon and it's working fine.

It sounds to me like the 'loginfo' script is unable to connect to the
freshcvs daemon because of permission problems between the two. Is it using a
Unix-domain socket? If so, the socket must be writable by everyone with
commit access, probably with 'a+rx'-style permissions. You may also be able
to debug this sort of thing by adding 'print' messages into the FreshCVS code
that gets run from the loginfo script, as these messages should go to the
console of the user performing the commit.

My suggestion would be to remove Buildbot from the equation by changing your
freshcvs config file to merely log change messages (instead of serving them
via PB to listeners like the buildmaster), as this sounds more like a
freshcvs issue than a buildbot issue.

To be honest, I haven't done much with FreshCVS for a year.. I'm still using
it on my home repositories, but I haven't touched the configuration since I
first set it up, and all the other buildbots I've set up recently have used
SVN or Arch or some email-based notification scheme.

hope that helps,

More information about the devel mailing list