Update and expand docs/ folder for EEs #10464
Conversation
|
Build failed.
|
|
|
||
| If you have installed dependencies inside of custom virtual environments in | ||
| a prior release, then have a look at this series of commands for help migrating | ||
| dependencies out of the venvs and into EEs. |
There was a problem hiding this comment.
maybe throw a sentence in about the -q option here?
There was a problem hiding this comment.
what's the -q option?
There was a problem hiding this comment.
I think running the commands with -q allows you to just redirect the output to a file that you can immediately use?
There was a problem hiding this comment.
That is not correct (but it's a good idea), it allows these to to be run without any output except the results from the functions (no tips or explanations, which are included in the default commands). This is specifically useful if you want to run them in combination or in a scripting style workup
There was a problem hiding this comment.
Thanks, updated the wording to be correct.
|
Build succeeded.
|
|
whoops, had a few errors after implementing the prior updates. Hopefully it should be good now. |
|
Build succeeded.
|
|
Build failed (gate pipeline). For information on how to proceed, see
|
|
regate |
|
Build succeeded (gate pipeline).
|
This has some new content about EE precedence, which I don't think we've documented anywhere else, thinking of @tvo318 here, content was developed by @jbradberry
(I think the numbers 2 and 3 in the global job default EE may still be subject to revision, just a warning)
@shanemcd #10324 is incorporated into this
This mentions @rebeccahhh's venv migration stuff, but I'm trying to write the absolute minimum possible while still mentioning migration.