[Buildbot-devel] SourceBaseCommand.sourcedatafile location

Marc-Antoine Ruel maruel at chromium.org
Sat Apr 21 13:31:17 UTC 2012

Note that Jorge is using the chromium's version of buildbot, which is at

I'm glad that sourcedata is going away. While an interesting optimization,
it's much safer to gather actual status from the slave.


Le 20 avril 2012 22:44, Tom Prince <tom.prince at ualberta.net> a écrit :

> So, the sourcedata file was originally stored in the workdir. but this
> was changed because various combinations of vcs+mode clobbered unknown
> files in the workdir, and also to avoid poluting the build directory, in
> case build scripts care about this.
> Looking at the master-side steps, it looks like none them store
> sourcedata, instead extracting enough data from the repository.
> Although it looks like cvs is currently broken in this respect (#2287).
> I'm not sure what the proper resolution to this should be.
>  Tom
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20120421/3ee1d21a/attachment.html>

More information about the devel mailing list