Ticket #814 (closed enhancement: fixed)
Add a SetPropertyFromEnv step that just fetches an env var from the slave
| Reported by: | tfogal | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.8.3 |
| Version: | 0.8.0 | Keywords: | |
| Cc: | kovarththanan.rajaratnam@… |
Description
It would be nice if FileUpload? expanded environment variables. That is, slavesrc would expand using the slave's env and masterdest would expand using the master's env.
One could always workaround this using BB properties, but sometimes you've already got the value you need in your env and this would make things a bit more convenient.
Change History
comment:1 Changed 3 years ago by dustin
- Summary changed from Expand environment variables in FileUpload to Add a SetPropertyFromEnv step that just fetches an env var from the slave
- Milestone changed from undecided to 0.8.+
comment:6 Changed 2 years ago by Dustin J. Mitchell
- Status changed from new to closed
- Resolution set to fixed
Merge branch 'server-source' of git://github.com/tomprince/buildbot
- 'server-source' of git://github.com/tomprince/buildbot: Handle with properties for the string in buildbot.steps.transfer.StringDownload?. Add slave commands to make and remove directories. Add SetPropertiesFromEnv? command, and slave side support. (closes #814)
(with whitespace cleanup)
Changeset: 6848682f29b9ca84694b0e47a07c0c9e87ebfeeb
Note: See
TracTickets for help on using
tickets.
![[Buildbot Logo]](/chrome/site/header-text-transparent.png)
We're going to stick to using properties - I don't want to try to reimplement shell variable expansion in the slave code. I think the case you are looking at is in #813, right?
That said, perhaps a SetPropertyFromEnv step (that does not use the shell) would be useful.