[Buildbot-devel] setting environment variables in build steps

Stefan Seefeld seefeld at sympatico.ca
Fri Nov 23 12:43:49 UTC 2007

Axel Hecht wrote:

> So, by default, buildername, buildnumber, branch, revision,  and
> slavename are set properties, see
> http://buildbot.net/trac/browser/buildbot/process/base.py#L258.

Yes, I have seen that list. (I'm a bit surprised to find such rather
domain-specific variables available in general. Not all builds rely on
revision control. Or may be they do...)

I was actually thinking that a set of variables including workdir are
common enough to be useful to expose, too.

> The only way to set more properties is to actually write custom
> buildsteps that do it,
> http://buildbot.net/repos/release/docs/buildbot.html#Build-Properties.
> Now, for workdir in particular, that would be a property on the
> buildstep, not the build. It sounds more logical to me to have an
> initial buildstep that would set, say, ALF_LIBRARY_BASE, and use that
> property to set the workdir for the step that actually creates alf,
> and then use the same base variable to set your ALF_LIBRARY_PATH for
> make check.

Hmm, couldn't WithProperties use the same kind of cascading that is used
for such variables that are available as defaults from the builder, but
can be redefined by steps ?

> As the current workdir for a step could be anything on the run, I'd
> rather not set that as a build property.

I agree. But if a WithProperties' lookup always starts at the step
level, it could Just Work in both cases.



      ...ich hab' noch einen Koffer in Berlin...

More information about the devel mailing list