1172591 - Add create_virtualenv(force_creation=True) for help disposing of mozharness' special venv as needed

Status: RESOLVED INACTIVE

(Release Engineering :: Applications: MozharnessCore, defect)

Description

[Selena Deckelmann :selenamarie :selena]

We have a local venv in build/venv for help with monitoring. 

I'm working on bug 1162230 which requires that directory to be blown away to properly test. Perhaps we should an an option to force recreating this virtualenv. May want to just make this happen as part of an ordinary clobber.

Comment 1

[Jordan Lund (:jlund)]

(In reply to Selena Deckelmann :selenamarie :selena from comment #0)
> We have a local venv in build/venv for help with monitoring. 
> 
> I'm working on bug 1162230 which requires that directory to be blown away to
> properly test. Perhaps we should an an option to force recreating this
> virtualenv. May want to just make this happen as part of an ordinary clobber.

I should note if we 'clobber' a job in a script and the venv dir is within {mozharness_repo}/build/ it will be removed already.

however jobs that are like desktop builds[1] that avail of buildbase.py[2] try to create the venv before we do any actions like clobber because it is called from the scripts __init__

[1] http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/[e-mail]-1a01777b1b98/try-linux-debug/try-linux-debug-bm78-try1-build365.txt.gz
[2] https://dxr.mozilla.org/build:mozharness/source/mozharness/mozilla/building/buildbase.py#547