FR: Variable to reference the absolute path of the build dir

[ipv6guru]

It is harder than it needs to be to setup build steps that can be used on different bots. I can think of two things that would go along way to making this easier:

1) Any ShellCommands? in steps should have a special placeholder that will be expanded to the absolute path of the workdir on that bot. For example, /bin/sh $WORKDIR$/../vendor/<blah blah blah> Would let me, portably, reference a peer directory to the work directory without having to know that the slave bot was installed to /home/buildbot/slave and the builder's basedir was 'builder', etc.

2) A map / dictionary of values set in a configuration on the slave that could be referenced by steps in a builder. For example, if I was trying to build a Java project using Ant, I need to set JAVA_HOME and ANT_HOME environment variables for my shell commands. However, these might be installed in different locations on different bots so it would be great if I could set them up when I configure the slave bot, rather than having to create more complex builders and knowing all the locations in the master's config file.

---

Dave Peterson dpeterson@…

Submitted: Nobody/Anonymous? ( nobody ) - 2005-01-27 06:50

[ipv6guru]

Moved from sourceforge

[beaugunderson]

Re: #1 I am running into this situation now. I want to reference the libraries that have been compiled using LD_LIBRARY_PATH so that the unit tests run using the newly-compiled version of the libraries but can't figure out how to get a variable containing the builddir.

[dustin]

Good thoughts .. who's going to implement?

[dustin]

wait, what about $PWD?