<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.python.buildbot.devel">
    <title>gmane.comp.python.buildbot.devel</title>
    <link>http://blog.gmane.org/gmane.comp.python.buildbot.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8315"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8314"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8312"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8309"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8307"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8303"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8301"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8294"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8293"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8290"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8286"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8281"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8280"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8274"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8271"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8270"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8267"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8265"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8263"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8260"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8315">
    <title>db.schedulers.classifyChanges relies on integritycheck</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8315</link>
    <description>&lt;pre&gt;Today I reconfigured buildbot (renamed schedulers) while there where some changes waiting for the treeStableTimer., there are some changes awaiting in the database.

 
Now the reconfiguration does not succeed as an internal error occurs during the creation of the scheduler:

The stacktrace in the buildbot.log contains an error "(InternalError) current transaction is aborted, commands ignored until end of transaction block"

The last buildbot source in this stacktrace is at File "/home/buildmaster/buildbot/buildbot-latest-mr-gui/master/buildbot/db/schedulers.py", line 45

The statement that follows looks good:

UPDATE scheduler_changes SET important=%(important)s WHERE scheduler_changes.objectid = %(objectid_1)s AND scheduler_changes.changeid = %(wc_changeid)s'

     {'wc_changeid': 934, 'important': 1, 'objectid_1': 39}

 
The error occurs in db.schedulers.classifyChanges. This method relies on the integrity check of the database. When an insert does not succeed then an update is performed. &lt;/pre&gt;</description>
    <dc:creator>Harry Borkhuis</dc:creator>
    <dc:date>2012-05-23T14:25:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8314">
    <title>Current State of glob/wildcards in FileUpload/Download steps</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8314</link>
    <description>&lt;pre&gt;I've found some old messages fron 2007 about FileUpload and Download and
globbing - but nothing since then.

Is there a suggested solution for handling globbing with both Upload and
Download ?


The reason being that while my build number is generated by Buildbot - the
software itself sets its version number - and I don't want that logic to
move since we can track it in SVN.


Since its only the upload/download steps that need to deal with the
specifics of filenames, would be useful to handle the case.


richard.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Buildbot-devel mailing list
Buildbot-devel-5NWGOfrQmneRv+LV9M&lt;/pre&gt;</description>
    <dc:creator>Richard Offer</dc:creator>
    <dc:date>2012-05-21T18:11:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8312">
    <title>using **kwargs with MasterShellCommand</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8312</link>
    <description>&lt;pre&gt;
Hi,

I am using Buildbot 0.8.6p1 with Twisted 12.0.0. I have a problem in 
using **kwargs with the MasterShellCommand.

I am trying the following:

class NewClass(MasterShellCommand):

     def __init__(self, **kwargs):
       self.arg1 = kwargs.get('arg1')
       self.arg2 = kwargs.get('arg2')
       print self.arg1
       print self.arg2
       MasterShellCommand.__init__(self, "")

     def start(self):
       self.command=[self.arg1 + 'somestring',
                           WithProperties("build-%s.tar.gz", "revision"),
                           self.arg2]
       return MasterShellCommand.start(self)

     def finished(self, result):
         ...

it is called

NewClass(arg1='path', arg2='string')

Everything is just fine when I am running

buildbot checkconfig
The print statements deliver the expected outputs. When I am running the 
buildstep the logfile shows

exceptions.TypeError: unsupported operand type(s) for +: 'NoneType' and 
'str'

So for some reason self.arg1 and self.arg2 are a None object &lt;/pre&gt;</description>
    <dc:creator>Jürgen Schulz-Brüssel</dc:creator>
    <dc:date>2012-05-16T15:05:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8309">
    <title>A question about multiple changes</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8309</link>
    <description>&lt;pre&gt;Hi there,

I am using buildbot as my CI tool. I have a question about multiple
changes. Hope anyone can help me. Thanks.

I use git repository to manage my code and use git_buildbot.py to send
changes to buildbot. Recently I find if multiple changes are sent, buildbot
only buids the first and the last changes.

For example, there are changes 1, 2, 3, 4. I am sure all of them are sent
to buildbot from the log. But buildbot only builds change 1 and 4. Change 2
and 3 are displayed on the waterfall view, but not built. I am wondering if
it's normal. I haven't found anything in documentation. Is there anybody
able to  help me figure out? Thanks.

Cheers,

Eric
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm&lt;/pre&gt;</description>
    <dc:creator>Eric Zhu</dc:creator>
    <dc:date>2012-05-16T08:16:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8307">
    <title>Trigger step</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8307</link>
    <description>&lt;pre&gt;I am looking at adding multirepo functionality to the triggerstep, but I am not sure about the sourcestamp attribute.

 
The Triggerstep can be configured with a SourceStamp dictionairy.  Is this only used to pass repository, branch and revision or is there other information passed to the step.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Buildbot-devel mailing list
Buildbot-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/buildbot-devel
&lt;/pre&gt;</description>
    <dc:creator>Harry Borkhuis</dc:creator>
    <dc:date>2012-05-11T14:55:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8303">
    <title>multirepo has landed!</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8303</link>
    <description>&lt;pre&gt;I just merged Harry's multirepo3 branch, which brings in the last of
the multirepo implementation.  This merge alone was 80 commits.  There
are doubtless still bugs and minor oversights, but nothing we can't
handle.

This has been a HUGE project.  Harry's been at it for quite a while
now, and his dedication and attention to detail show in the results.

  Thank you, Harry -- and Benoît, too! -- for a substantial
contribution to Buildbot.

This puts us on the final approach to 0.8.7, so shut down your
approved electronic devices, check that your seat-backs and tray
tables in the full upright and locked position, and find some time in
your schedule to test out the master branch.  We're going to need all
the help we can get to shake out the last few bugs, and avoid a
0.8.7p1!  As things settle out a bit more, I'll make some tarballs for
download and announce them here, for easy pip-installing.

Seriously, QA has been the biggest pain-point for releasing Buildbot:
most of the testing happens *after* a release.  &lt;/pre&gt;</description>
    <dc:creator>Dustin J. Mitchell</dc:creator>
    <dc:date>2012-05-09T04:42:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8301">
    <title>"patch" command not being found on Windows</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8301</link>
    <description>&lt;pre&gt;
I'm trying to get the Try scheduler to work , but my Windows build slave is having a problem finding the patch executable

remoteFailed: [Failure instance: Traceback from remote host -- Traceback (most recent call last):
  File "c:\BOT\win32\bin\lib\site-packages\buildbot_slave-0.8.6p1-py2.7.egg\buildslave\runprocess.py", line 201, in processEnded
    self.command.finished(sig, rc)
  File "c:\BOT\win32\bin\lib\site-packages\buildbot_slave-0.8.6p1-py2.7.egg\buildslave\runprocess.py", line 687, in finished
    d.callback(rc)
  File "c:\BOT\win32\bin\lib\site-packages\twisted-12.0.0-py2.7-win32.egg\twisted\internet\defer.py", line 368, in callback
    self._startRunCallbacks(result)
  File "c:\BOT\win32\bin\lib\site-packages\twisted-12.0.0-py2.7-win32.egg\twisted\internet\defer.py", line 464, in _startRunCallbacks
    self._runCallbacks()
--- &amp;lt;exception caught here&amp;gt; ---
  File "c:\BOT\win32\bin\lib\site-packages\twisted-12.0.0-py2.7-win32.egg\twisted\internet\defer.py", line 551, in _runCallbacks
    current.r&lt;/pre&gt;</description>
    <dc:creator>Richard Offer</dc:creator>
    <dc:date>2012-05-06T19:03:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8294">
    <title>column headings showing 'building' when notbuilding</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8294</link>
    <description>&lt;pre&gt;Sometimes my column headings show that a build is 'building' even when it is done.  Has anyone seen that before?  Should I submit a bug?
(see attached where only builders 1 and 5 are actively building when 6, 9 &amp;amp; 10 are finished)
I am running 0.8.5 on linux .. I know I should upgrade and will be doing that sometime soon.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Buildbot-devel mailing list
Buildbot-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/buildbot-devel
&lt;/pre&gt;</description>
    <dc:creator>Todd Cooper</dc:creator>
    <dc:date>2012-05-04T17:19:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8293">
    <title>Using Properties numerically</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8293</link>
    <description>&lt;pre&gt;


I need/want to be able to use a property value numerically, i.e.

        set_properties = { 
            'SAUSAGEBOT_BUILDID' : 40000 + int( buildbot.process.properties.WithProperties("%(buildnumber:-0000)s") ), 
        },


Obviously that doesn't work or anything close to that…


Can I get a basic string or int type out of WithProperties() ?


[ View from the 1 week buildbot newbie ]

It seems to be something that we can use - but I've really had a hard time getting it to work with the existing build code.

Our existing build code (using bamboo) is all environment variable driven, trying to get Properties in sync with environment variables has proved to be magic - and not the good type…

I think the complexity has been trying to provide support for both individual and system builds (the system build triggers all the individual builds) - and I want to be able to use a single top level build-id for all generated products (split across each of the builders) - and that id is not the revision version.

&lt;/pre&gt;</description>
    <dc:creator>Richard Offer</dc:creator>
    <dc:date>2012-05-04T17:08:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8290">
    <title>Sending email depending on completion of onebuilder</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8290</link>
    <description>&lt;pre&gt;I don't see how to program the emailer to send email to one set of people on completion of one builder and another set of people with another builder.

Anyone have any ideas?
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Buildbot-devel mailing list
Buildbot-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/buildbot-devel
&lt;/pre&gt;</description>
    <dc:creator>Todd Cooper</dc:creator>
    <dc:date>2012-05-01T14:34:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8286">
    <title>create-master error</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8286</link>
    <description>&lt;pre&gt;I just started setting up buildbot last week.  I think I incorrectly installed something because I can't even get "buildbot create-master -r c:\buildbot_workarea" to work.



Here is the message I am seeing



buildbot create-master -r c:\buildbot_workarea



mkdir c:\buildbot_workarea

creating master.cfg.sample

populating public_html/

Traceback (most recent call last):

  File "C:\Python27\lib\site-packages\twisted\internet\defer.py", line 290, in addCallbacks

   self.runCallbacks()

  File "C:\Python27\lib\site-packages\twisted\internet\defer.py", line 551, in _runCallbacks

    current.result = callback(current.result, *args, **kw)

  File "C:\Python27\lib\site-packages\twisted\internet\base.py", line 426, in _continueFiring

    callable(*args, **kwargs)

  File "C:\Python27\lib\site-packages\buildbot-0.8.6p1-py2.7.egg\buildbot\scripts\runner.py", line 36, in async

    d = defer.maybeDefferred(f, *args, **kwargs)

--- ( exception caught here) ---

  File "C:\Python27\lib\site-packages\twisted\intern&lt;/pre&gt;</description>
    <dc:creator>Catherine Knutson</dc:creator>
    <dc:date>2012-04-30T17:29:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8281">
    <title>Buildbot 0.8.6p1 not giving me "Force Build"</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8281</link>
    <description>&lt;pre&gt;I've updated my 0.8.3 Buildbot system to the current release (0.8.6p1).  Both
my master and my slave are running this version.  I've re-initialized the
master and copied my original 'master.cfg' file into place with the
deprecation warnings address.

When I start the master, and then start the slave, I'm not being given the
option to "Force Build" on any of the slaves.  All it allows is "Ping".  Any
reason why I should be seeing this?  I suspect there's something in my
master.cfg that is causing this issue, but there's nothing in the log to
indicate any issues.

Anybody else run into this when updating to 0.8.6?

Render me gone,                       |||
Bob                                 ^(===)^
---------------------------------oOO--(_)--OOo---------------------------------
    I'm not so good with advice...can I interest you in a sarcastic comment?


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways &lt;/pre&gt;</description>
    <dc:creator>Bob Hood</dc:creator>
    <dc:date>2012-04-30T00:45:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8280">
    <title>Help with p4 master side step creation</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8280</link>
    <description>&lt;pre&gt;Greetings,

I'm working on creating a master side source step for perforce. (p4).

I'm running into an issue where the parameter "p4client" is not getting rendered.

Here's the current code:
https://github.com/bdbaddog/buildbot/blob/p4_master_source_step/master/buildbot/steps/source/p4.py

I'm sure there's something simple I'm not doing, but the following call to P4:
        builder.addStep(buildbot.steps.source.p4.P4(p4port = p4port,
                                                    p4client='buildbot_%(slave)s_%(builder)s',
                                                    p4user = p4user,
                                                    p4base = branchP4Path+'/',
                                                    p4extra_views = p4extra_views,
#                                                    mode = 'incremental',
                                                    mode = 'full',
                                                    timeout = 3600))


Yields the p4client being unrendered, even on&lt;/pre&gt;</description>
    <dc:creator>William Deegan</dc:creator>
    <dc:date>2012-04-30T00:17:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8274">
    <title>Buildbot newbie question on complex setup</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8274</link>
    <description>&lt;pre&gt;
I'm researching replacing our multi-agent Bamboo CI server with a more integrated solution.

I've looked at Jenkins and am now evaluating Buildbot.


Its starts of well since I much prefer to write code to do something than click in a web browser :-)



But I'm missing the bit that goes from a simple configuration to a complex one.


Here's what I have so far:

One build factory for each configuration (linux32, linux64, windows)

But this is what I need to piece together

the linux64 build is product master package
the linux32 and windows (on dedicated slaves) builds need to build and their results (RPMs, MSIs) need to be passed to the linux64 build factory
the linux64 build then needs to start a final job on another agent (running VMware Studio) to take all the pieces and package them into an OVF.

Obviously the linux32 and windows builds should be in a BuildSet - but I can leave that for now…

What is the best way to share "artifacts" between the various build factories ?


I've looked at the trigge&lt;/pre&gt;</description>
    <dc:creator>Richard Offer</dc:creator>
    <dc:date>2012-04-28T19:06:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8271">
    <title>development branch for 0.9.0</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8271</link>
    <description>&lt;pre&gt;It's time to get serious about work on Buildbot-0.9.0.  The
DevelopmentPlan page on the wiki describes the plan, and it's pretty
ambitious.

I've just pushed a new "nine" branch to the organization repository:
  https://github.com/buildbot/buildbot/commits/nine
so we can start sharing and collaborating on this branch.  The rules
I'll be following on this branch are what you'd expect for a shared
development branch: no history rewriting, but also no promises about
any kind of compatibility - we can rename functions, change message
definitions, and so on to our hearts' content.  Tests should pass on
each commit, and pyflakes should not produce any output.

In the short term, I'm going to try to rush ahead to make a basic
implementation of the data API, since that will likely be fundamental
to Naveen's work on the JavaScript frontend.

Follow along?  Pull requests and extra code will be *very* much appreciated.

Dustin

------------------------------------------------------------------------------
Live Security&lt;/pre&gt;</description>
    <dc:creator>Dustin J. Mitchell</dc:creator>
    <dc:date>2012-04-28T03:55:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8270">
    <title>GSoC project: Implementing a new Master-SlaveProtocol.</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8270</link>
    <description>&lt;pre&gt;Hi,

I am Saurabh Kumar, I introduced myself to the list a few weeks ago.
My proposal 'Implementing a New Master-Slave Proposal' was accepted as
a GSoC project this year. As expected, I'm pretty excited about it. :)
My proposal is available on melange[1]. A rough schedule along with
the proposal is placed under version control as a gist[2].  I'll be
finalizing the schedule in the community bonding period. My work will
be online on my buildbot fork on github[3], and this will be a good
way to follow my progress. I'll also post updates here on the mailing
list after reaching significant milestones. I'll also be online on
#buildbot nearly always, where my nick is sa1. I'll be glad to receive
suggestions or to answer questions, by email or on irc.

--Saurabh

[1]: http://www.google-melange.com/gsoc/project/google/gsoc2012/saurabh_kgp/9002
[2]: https://gist.github.com/2513224
[3]: https://github.com/sa1/buildbot

------------------------------------------------------------------------------
Live Security Virtual &lt;/pre&gt;</description>
    <dc:creator>Saurabh Kumar</dc:creator>
    <dc:date>2012-04-27T21:13:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8267">
    <title>Properties on force build do not override "default" ones of build slaves ? (0.8.5)</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8267</link>
    <description>&lt;pre&gt;Hi,

in my buildbot configuration, I provide a few properties to my build
slaves as default values.

(this is the example form buildbot docs, since my script is on a
different machine)

c['slaves'] = [
    BuildSlave('bot-solaris', 'solarispasswd',
                properties={ 'os':'solaris' }),
]


Then I tried to run force a build via the web frontend and tried to
provide a different value to one of the properties that are listed in my
buildslave configuration.
However, it seems that the settings in the buildslave configuration take
precedence over the ones in the web form. It seems the latter ones are
simply ignored ( For debugging, I wrote all propery settings to a
logfile in my very first buildstep).
When I remove the properties in the buildslave configuration, they are
correctly set to the values provided in the web form.

In the example, settings "os" as a custom property to some other value
in the web frontend would not work. The property "os" would still
contain "solaris" when queried in the first b&lt;/pre&gt;</description>
    <dc:creator>Johannes Stallkamp</dc:creator>
    <dc:date>2012-04-25T14:28:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8265">
    <title>env dict passed to Source steps ignored inbuildslaves?</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8265</link>
    <description>&lt;pre&gt;Hi list,
I was just trying to set up the PATH env variable for a source step, but it
didn't seem to have an effect at runtime, based on what the logs showed.

Correct me if I'm wrong, but it seems to me like the env dictionary passed
to subclasses of buildbot.steps.source.oldsource.Source is being ignored on
the slave-side's buildslave.commands.base.SourceBaseCommand.setup(). In
particular, it's doing "self.env = os.environ.copy()" and completely
ignoring what was passed to it.

Assuming this is what's causing my own env to be ignored, is there a good
reason for this?

Thanks,
Jorge
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/______________________________________&lt;/pre&gt;</description>
    <dc:creator>Jorge Gonzalez</dc:creator>
    <dc:date>2012-04-24T16:38:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8263">
    <title>Wait for finish unless offline</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8263</link>
    <description>&lt;pre&gt;Hi,

Some of my current builder setups involve a builder triggering a list of 
other builders with waitForFinish=True set. This works fine, but it's 
possible that one or more of the triggered builders could be offline, 
and in this case I don't want the triggering builder to wait for the 
offline builder(s).

Does anyone know if it's possible to have the triggering builder only 
wait for online builders / skip triggering offline builders? Or achieve 
this behaviour some other way?

If it's not currently possible, does anyone have advice on patching this 
in? E.g. would it be better to add it as an option to the Trigger step, 
or the Triggerable builder, or..?

Thanks,
Thomas


------------------------------------------------------------------------------
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
&lt;/pre&gt;</description>
    <dc:creator>Thomas Middeldorp</dc:creator>
    <dc:date>2012-04-23T01:53:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8260">
    <title>Mail Handler not sending out notifications</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8260</link>
    <description>&lt;pre&gt;Hey List,

Anyone know why the mail handler isnt sending out notifications on the
following config in master.cfg

mn = MailNotifier(fromaddr="buildbot-/K3FCmxHHlvQT0dZR+AlfA&amp;lt; at &amp;gt;public.gmane.org",
         sendToInterestedUsers=False, mode='change',
         extraRecipients=["buildstatus-/K3FCmxHHlvQT0dZR+AlfA&amp;lt; at &amp;gt;public.gmane.org"],
         useTls=True, relayhost="localhost", smtpPort=2525)

Nothing else was in the google's and docs.
------------------------------------------------------------------------------
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-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/buildbot-devel
&lt;/pre&gt;</description>
    <dc:creator>Shariar Kazi</dc:creator>
    <dc:date>2012-04-21T14:36:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.buildbot.devel/8256">
    <title>SourceBaseCommand.sourcedatafile location</title>
    <link>http://comments.gmane.org/gmane.comp.python.buildbot.devel/8256</link>
    <description>&lt;pre&gt;Hi there,
I'm making use of factory workdir functions[1]. This means that the workdir
passed to build steps created by these factories, including source steps,
is subject to change at runtime depending on what the provided function
returns. As the documentation[1] suggests, this is useful to keep different
dedicated workdirs for different repositories.

Now, if the goal of the contents in SourceBaseCommand.sourcedatafile is to
provide some sort of fingerprint of the origin of the source inside some
workdir (and I can be wrong about this), wouldn't it make sense to keep
sourcedatafile within the workdir it refers to? In other words, if it's
possible for a builder's source step to check code out from different
repositories into different workdirs, wouldn't it make sense to keep
separate sourcedatafiles to identify the origin of their code in them?

Currently sourcedatafile lives under SourceBaseCommand's
self.builder.basedir. Wouldn't it make sense to have it reside
under self.builder.basedir/self.workdir?

By&lt;/pre&gt;</description>
    <dc:creator>Jorge Gonzalez</dc:creator>
    <dc:date>2012-04-21T00:46:24</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.python.buildbot.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.python.buildbot.devel</link>
  </textinput>
</rdf:RDF>

