Mercurial Mercurial > corpus_parole / changeset
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset | raw | zip | gz | bz2 | help
Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
put virtualenv activation during build in comment. That means that for the moment the build machine must be provisionned beforehand, or ansible must be available globally
authorymh <ymh.work@gmail.com>
Thu, 03 Nov 2016 09:44:11 +0100
changeset 390 f4fed295115b
parent 389 2204faa0b41a
child 391 4f6118afabee
put virtualenv activation during build in comment. That means that for the moment the build machine must be provisionned beforehand, or ansible must be available globally
build/build.sh file | annotate | diff | comparison | revisions 
--- a/build/build.sh	Thu Nov 03 04:43:18 2016 +0100
+++ b/build/build.sh	Thu Nov 03 09:44:11 2016 +0100
@@ -50,16 +50,16 @@
     echoblue "---> checking vagrant"
     if vagrant status | grep -q -v "running"; then
         echoblue "---> starting vagrant"
-        if which virtualenvwrapper.sh > /dev/null 2>&1 ; then
-            echoblue "---> activating ansible"
-            source `which virtualenvwrapper.sh`
-            workon ansible
-        fi
+        # if which virtualenvwrapper.sh > /dev/null 2>&1 ; then
+        #     echoblue "---> activating ansible"
+        #     source `which virtualenvwrapper.sh`
+        #     workon ansible
+        # fi
         vagrant up
         VAGRANT_STARTED=true
-        if type -t deactivate > /dev/null 2>&1 ; then
-            deactivate
-        fi
+        # if type -t deactivate > /dev/null 2>&1 ; then
+        #     deactivate
+        # fi
     fi
 
     echoblue "---> done"
corpus_parole