[Buildbot-devel] Buildbot try with mercurial

Gunnison, Brian brian.gunnison at intel.com
Fri Jun 4 21:10:05 UTC 2010

Not sure I understand "invasive" in this context (especially as this is my first post in this context...).

This method perhaps should be default in that we compress the diff for any VCS. This way the file is reliable across the net. I cringe thinking about a char error in a diff file.



From: Dustin Sallings [mailto:dustin at spy.net]
Sent: Friday, June 04, 2010 1:43 PM
To: Gunnison, Brian
Cc: buildbot-devel at lists.sourceforge.net
Subject: Re: [Buildbot-devel] Buildbot try with mercurial

On Jun 4, 2010, at 10:42, Gunnison, Brian wrote:

I'd like to fix "buildbot try" to work well with mercurial. I'd like to send a mercurial "bundle" instead of a patch when the developer issues "buildbot try". How can I send a file instead of a text diff?

            That sounds pretty invasive.

            For example, I've got a GAE app that displays realtime progress of builds using the webhook status receiver which uses the sourcestamp's patch as part of its display.  Things like this would all have to deal with "displaying" the patch.

Dustin Sallings

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20100604/8f7805bb/attachment.html>

More information about the devel mailing list