openstack/project-config
Code Issues Proposed changes

translations: Always setup venv

Browse Source 
With healthcheck generation, we need the venv containing the subunit
files always to be set up.

Change-Id: I82531fff49e0258c2934315f11f2dd2064f308ea
This commit is contained in:
Andreas Jaeger 2016-06-07 10:06:51 +02:00
parent e6cb1cd8b7
commit 483db9e7b5
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
jenkins/scripts/propose_translation_update.sh
View File

@ -192,6 +192,9 @@ setup_git
# Check whether a review already exists, setup review commit message.
setup_review "$BRANCH"
# Setup venv - needed for all projects for subunit
setup_venv
case "$PROJECT" in
api-site|ha-guide|openstack-manuals|operations-guide|security-doc)
init_manuals "$PROJECT"
@ -205,7 +208,6 @@ case "$PROJECT" in
;;
*)
# Common setup for python and django repositories
setup_venv
setup_loglevel_vars
handle_python_django $PROJECT python
handle_python_django $PROJECT django

4
jenkins/scripts/upstream_translation_update.sh
View File

@ -39,6 +39,9 @@ fi
setup_git
# Setup venv - needed for all projects for subunit
setup_venv
# Project setup and updating POT files.
case "$PROJECT" in
api-site|ha-guide|openstack-manuals|operations-guide|security-doc)
@ -67,7 +70,6 @@ case "$PROJECT" in
;;
*)
# Common setup for python and django repositories
setup_venv
# ---- Python projects ----
module_names=$(get_modulename $PROJECT python)
if [ -n "$module_names" ]; then