Closed jjr840430 closed 6 years ago
@drystone I think it would be better to modify the configuration of retrace
at run-time.
Then is it possible to use the wrapper script in this case?
@jjr840430 , no it won't be possible to modify config from the script.
I think it would be better to avoid the temporary file creation - you either have to create a temporary file with no way of deleting or use a predefined path (~/.something) that can cause problems if you have more than one instance of retrace
.
How about modifying get_config
to add the config from the environment to the config list and then load the config file as before, adding to the list?
It's moot anyway as config is about to receive a major overhaul.
Guys, Agree with @drystone . To summarize:
Agreed, guys. I didn't regard the case of multiple instances of retrace. Thanks for your advice.
Can't set status; build failed.
Can't set status; build succeeded.
@jjr840430 sorry I didn't have time earlier to review this. I agree that a temporary file is not the best way because that currently can be done outside of Retrace. Moving that into Retrace itself does not improve things.
And I also agree with configuration setup flow that @ikolomi described.
@erikbor @jjr840430 are we ready to merge this?
@ronaldtse I need to modify something here. I will let you know after doing.
Currently retrace
is parsing the configurations based on file pointer
, so it needs to modify the most part of config parsing.
If we need to have new config by JSON, then this pull request may be ignored.
Implemented issue #334