[Buildbot-devel] copying information between steps or schedulers

[Stefan Seefeld]

A.T.Hofkamp wrote:

> Hmm.
> Not sure that your proposal is a good direction; having to write a 
> derived class doesn't immediately strike me as easy-to-adopt (that is, I 
> have a hard time imagining a busy sys-admin taking the time to learn 
> enough Python to set up buildbot by writing a set of derived classes).

Yeah, I'm not sure whether this is a good idea either. I was just wondering
about ways to get the desired behavior without too much change to buildbot
itself.
Having a more concise (declarative ?) way to do the same would certainly
be nice.

> Also, assuming that buildmaster and buildslave are at two different 
> machines, the derived class seems to be at the wrong machine for easily 
> interfacing with the program it is supposed to control. It would be much 
> easier (probably) if the new object would be at the buildslave.

I don't think so. IIUC, Step instances live in the master, commands live
in both. What I suggest is not to replace existing steps, but to wrap ('decorate')
them such that their commands are set at runtime, not configuration time.

> While there seems the be room for improvement, your thought experiment 
> was quite useful for me; it gave some direction for the solution. Also, 
> your remark about initialization versus runtime is a very good one.

Great. I'm glad I can contribute. I still wonder though what Brian thinks
about this, in particular whether there is anything that could be done by
the buildbot infrastructure to support context sharing (across steps, but
also across builders / schedulers).

Thanks,
		Stefan