Feature: make dry run output readable (and also of eb --search)#781
Conversation
Signed-off-by: Fotis Georgatos <[email protected]>
… etc Signed-off-by: Fotis Georgatos <[email protected]>
Signed-off-by: Fotis Georgatos <[email protected]>
Signed-off-by: Fotis Georgatos <[email protected]>
Signed-off-by: Fotis Georgatos <[email protected]>
|
Automatic reply from Jenkins: Can I test this? |
…o feature_make_dry-run_output_readable
|
Jenkins: ok to test |
There was a problem hiding this comment.
You should pick up the robot path instead of grabbing the value of some random environment variable $CFGS.
Try and take into account somehow that the robot path might contain multiple entries, separated by os.pathsep (:).
There was a problem hiding this comment.
Also, what happens if $CFGS is not set here?
There was a problem hiding this comment.
OK, first, thanks for looking into this early on, because we'll need to time to settle on the preferred design.
The whole point of this, is to make output of --dry-run & eb --search more readable for the newcomers.
I see no way to avoid ambiguity if I rely on robotpath exclusively, because trimming down the output on the basis of that, creates confusion when an easyconfig exists on more than one paths. What's your stance on that? Any ideas to offer?
It's important to settle at this first, because that affects all the rest of the changes.
(and surely agree, that it should behave reasonably if CFGS is not defined ;-)
There was a problem hiding this comment.
OK, I hadn't realized that $CFGS is now considered "random" variable, because in early versions of the tool (I think including v1.0) it was defined as the default robotpath, no? Admittedly, this code will not handle gracefully the situation of a multicomponent robotpath.
|
how does this get affected by #786 ? Unless you come up with some other idea, I think we will be forced to settle to some convention (eg. match against variables finishing in |
…o feature_make_dry-run_output_readable
Signed-off-by: Fotis Georgatos <[email protected]>
This reverts commit e2dac32.
Signed-off-by: Fotis Georgatos <[email protected]>
|
What's with the CFGs variable? Why do you need this here? Can't you set EASYBUILD_ROBOT ? I see no way this is getting merged in with the current CFGSVAR = 'CFGS' configuration should be don in the config file, add the CFG to the 'path' in the search_file, and allow it to take a template or something, and then set the template in the config file. This way when other people want another output format they can easily change it, without having to change the python code again. |
|
@JensTimmerman: No worries, I'm on it. :-) |
…readable Conflicts: easybuild/main.py
…=' prefix in printed messages
…rch pick up robot paths, align output of search/dry-run, use options.search_short and options.dry_run_short
add --dry-short-short/-D and --search-short-S options, clean up implementation, add unit tests
|
one further improvement, could be to have the output of --search actually report also in markdown/github style, * [x], |
|
@fgeorgatos: I feel that goes beyond the intention of So, this should be ready to go, you think? Have you played with it? |
|
I'm happy with this, the unit tests are happy, so merging it in. Thanks for initiating this @fgeorgatos! |
…eadable Feature: make dry run output readable (and also of eb --search)
|
cool! sorry for being slow to reply... i am still on the road for today ;-)
|
Here is the why of this:
(sry, but I couldn't really read the other kind of output)