Closed
Bug 1030768
Opened 11 years ago
Closed 7 years ago
Add the config.json.in file from TPS package as package_data
Categories
(Testing Graveyard :: TPS, defect)
Testing Graveyard
TPS
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: cosmin-malutan, Unassigned)
Details
Right now we add the config.json.in as data_files, this limits us to be in the same directory with the setup.py script when installing the package.
if we switch to
>package_data={'tps': ['config/config.json.in']}
we avoid this.
Also the files that are created by the setup process are not created in the same place with the script but in the directory from where we called the script, that means we have to update the cleanup from create_venv.py too:
https://github.com/mozilla/gecko-dev/blob/master/testing/tps/create_venv.py#L154
Comment 1•7 years ago
|
||
Realistically, I don't think we'll have cycles to refactor this. The existing packaging setup seems to work OK for automation (it's running in a Docker container now).
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•