[Buildbot-devel] env variables from last step

[Kevin Funk]

On Friday 07 November 2014 11:33:07 Benoît Allard wrote:
> On 11/07/2014 08:39 AM, Kevin Funk wrote:
> > On Wednesday 05 November 2014 13:08:55 Nachaat Hassis wrote:
> >> Hello, im facing this problem: I have an executable which sets
> >> for me many env variables (can't change that since its a tool
> >> which comes with a workbench). is there a way to execute that
> >> executable and run the next step in the same env?
> >> 
> >> thanks for your help, cheers.
> > 
> > Heya,
> > 
> > There's a pretty generic and working solution I've been using for
> > several months already. This solution is basically extracting the
> > current env of a step into a property (using SetProperty + some
> > extract_fn), which can then just be reused in consecutive steps.
> > 
> > It has been discussed on SO: http://stackoverflow.com/a/17721123
> > 
> > PS: I'm all for bringing some native support for this in Buildbot
> > itself, though. I think it's a fairly valid use-case.
> 
> I believe this is indeed a common trouble. Think "virtualenv", or
> think Microsoft's "vcvarsall.bat".
> 
> Would you mind trying to elaborate Github Pull-Request with that ? I'd
> be glad to assist you, would you need so !
> 
> Regards,
> Ben.

I think there needs to be some discussion first -- how can we integrate this 
more into Buildbot?

My concerns about the approach used on SO:
* Requires you to touch every step that follows the one setting up the env
  (by modifying the step's env parameter). I'd like to avoid that.
* Clutters the property listing on build views
  (you'll see the whole environment as property value, which can be huge)

Greets

-- 
Kevin Funk | kevin.funk at kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel. Germany +49-30-521325470, Sweden (HQ) +46-563-540090
KDAB - Qt Experts - Platform-independent software solutions