Closed
Bug 822369
Opened 13 years ago
Closed 9 years ago
Investigate running mock commands from a generated script
Categories
(Release Engineering :: General, defect, P4)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: jhopkins, Unassigned)
Details
(Whiteboard: [mock][cleanup])
Mock commands and environment variables are currently passed to mock as a single line command string. One issue with this approach is the environment variables get interpolated by WithProperties.
A cleaner way of handling this would be to generate a temporary shell script that exports environment variables and runs the desired command. Then the call to mock only needs to include the path to that shell script. Use of the shell's 'set -x' would print the commands as they are run to aid in troubleshooting.
|
||
Updated•13 years ago
|
OS: Mac OS X → Linux
Priority: -- → P4
Hardware: x86 → x86_64
Whiteboard: [mock][cleanup]
|
Assignee | |
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
|
|
||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
|
|
Assignee | |
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•