Handle operations-guide and contributor-guide

Documentation projects are whitelisted. Since operations-guide and
contributor-guide has a normal "doc/source" setup, we can use the
generic handling of this and just extend the whitelist.
Instead of having the whiteliste in two places, move it in a central
shared place.

This will handle operations-guide and contributor-guide the same way
as horizon, openstack-ansible, and openstack-helm.

Change-Id: Ie1065b7d4ad47dee738568c70df28a5cdaa6f6f7
This commit is contained in:
Andreas Jaeger 2018-11-09 16:20:02 +01:00
parent eb544f7708
commit 135fb6a31a
3 changed files with 11 additions and 4 deletions

View File

@ -36,6 +36,14 @@ INVALID_PO_FILE=0
# set to 0 on successful run.
ERROR_ABORT=1
# List of repos that have doc/source translated, we test with a smaller
# set for now.
DOC_TARGETS=('contributor-guide'
'horizon'
'openstack-ansible'
'openstack-helm'
'operations-guide')
# We need a UTF-8 locale, set it properly in case it's not set.
export LANG=en_US.UTF-8

View File

@ -176,8 +176,8 @@ function handle_python_django_project {
# Handle project doc proposals
function handle_project_doc {
local project=$1
# doing only things in the test repos for project doc translation
if ! [[ "$project" =~ ^(horizon|openstack-ansible|openstack-helm)$ ]]; then
# Doing only things in the test repos for project doc translation
if ! [[ ${DOC_TARGETS[*]} =~ "$project" ]]; then
return
fi
# setup_project and pull_from_zanata are already done

View File

@ -115,9 +115,8 @@ case "$PROJECT" in
done
fi
# ---- Documentation ----
# Let's test this with some repos :)
DOC_TARGETS=('horizon' 'openstack-ansible' 'openstack-helm')
if [[ -f doc/source/conf.py ]]; then
# Let's test this with some repos :)
if [[ ${DOC_TARGETS[*]} =~ "$PROJECT" ]]; then
extract_messages_doc
ALL_MODULES="doc $ALL_MODULES"