【问题标题】:CircleCI not picking up environment variable defined in run step?CircleCI 没有选择运行步骤中定义的环境变量?
【发布时间】:2018-11-09 20:52:52
【问题描述】:

我正在尝试为 Django 项目运行 CircleCI 测试,其中 manage.py 确定要从环境变量 @ 应用的 settings.py 的版本(development.pystaging.pyproduction.py) 987654327@。以前,ENV_ROLE 如果未定义,则默认设置为 development,但我正在对其进行更改,以便 Django 在未定义时抛出 ImproperlyConfigured 错误。

为了使测试通过,我需要在我们的 CircleCI 测试环境中定义 ENV_ROLE 环境变量。在https://circleci.com/docs/2.0/env-vars/#setting-an-environment-variable-in-a-step 之后,我在run 步骤中添加了以下内容:

      - run:
          environment:
            ENV_ROLE: development

但是,我仍然从 CircleCI 收到此错误:

#!/bin/bash -eo pipefail
cd lucy-web
source venv/bin/activate
python manage.py compilescss --verbosity 0
python manage.py collectstatic --clear --no-input --verbosity 0
flake8
python manage.py test
Traceback (most recent call last):
  File "/root/lucy/lucy_web/lucy-web/env.py", line 5, in <module>
    ENV_ROLE = os.environ['ENV_ROLE']
  File "/usr/local/lib/python3.6/os.py", line 669, in __getitem__
    raise KeyError(key) from None
KeyError: 'ENV_ROLE'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "manage.py", line 4, in <module>
    from env import ENV_ROLE
  File "/root/lucy/lucy_web/lucy-web/env.py", line 8, in <module>
    "No 'ENV_ROLE' environment variable is defined. "
django.core.exceptions.ImproperlyConfigured: No 'ENV_ROLE' environment variable is defined. Please define it as 'development', 'staging', or 'production'.
Exited with code 1

这是完整的.circleci/config.yml

version: 2
jobs:
  build:
    working_directory: ~/lucy/lucy_web/
    docker:
      - image: python:3.6.5
        environment:
          DATABASE_URL: ...
      - image: jannkleen/docker-postgres-gis-hstore
        environment:
          POSTGRES_USER: ...
          POSTGRES_DB: ...
      - image: redis:4.0.9-alpine
    steps:
      - checkout
      - restore_cache:
          key: deps1-{{ .Branch }}-{{ checksum "lucy-web/requirements.txt" }}
      - run:
          name: Install Python deps in a venv
          command: |
            cd lucy-web
            python3 -m venv venv
            . venv/bin/activate
            pip3 install -r requirements.txt
      - save_cache:
          key: deps1-{{ .Branch }}-{{ checksum "lucy-web/requirements.txt" }}
          paths:
            - "venv"
      - run:
          environment:
            ENV_ROLE: development
          command: |
            cd lucy-web
            source venv/bin/activate
            python manage.py compilescss --verbosity 0
            python manage.py collectstatic --clear --no-input --verbosity 0
            flake8
            python manage.py test
      - store_artifacts:
          path: test-reports/
          destination: tr1
      - store_test_results:
          path: test-reports/
  app_test:
    working_directory: ~/lucy/lucy_app
    docker:
      - image: node:8
    steps:
      - checkout
      - run:
          command: |
            cd lucy-app
            yarn install
            yarn lint
            yarn jest
workflows:
  version: 2
  build_and_test:
    jobs:
      - build
      - app_test

Django项目有修改manage.py:

#!/usr/bin/env python
import os
import sys
from dotenv import load_dotenv, find_dotenv

if __name__ == "__main__":
    # Set environment variables from .env file
    load_dotenv(find_dotenv())

    # Determine which settings to apply (development, staging, or production)
    from env import ENV_ROLE
    os.environ.setdefault("DJANGO_SETTINGS_MODULE", f"lucy.settings.{ENV_ROLE}")
    try:
        from django.core.management import execute_from_command_line
    except ImportError:
        # The above import may fail for some other reason. Ensure that the
        # issue is really that Django is missing to avoid masking other
        # exceptions on Python 2.
        try:
            import django  # noqa: F401
        except ImportError:
            raise ImportError(
                "Couldn't import Django. Are you sure it's installed and "
                "available on your PYTHONPATH environment variable? Did you "
                "forget to activate a virtual environment?"
            )
        raise
    execute_from_command_line(sys.argv)

其中env.py 检查是否定义了ENV_ROLE 环境变量,否则抛出ImproperlyConfigured 错误:

import os
from django.core.exceptions import ImproperlyConfigured

try:
    ENV_ROLE = os.environ['ENV_ROLE']
except KeyError:
    raise ImproperlyConfigured(
        "No 'ENV_ROLE' environment variable is defined. "
        "Please define it as 'development', 'staging', or 'production'.")

我不明白为什么 CircleCI 没有“拾取”ENV_ROLE 环境变量?我的语法或对文档的理解有问题吗?

【问题讨论】:

  • 您可以尝试在作业级别而不是步骤级别设置变量吗?
  • 我会尝试在命令的第一行添加env 以打印出完整的环境,并查看是否设置了ENV_ROLE

标签: python django yaml circleci


【解决方案1】:

我在使用 circleCI + GAE 时遇到了类似的问题;我认为我在 .circleCI/config.yml 中设置的变量从未真正进入应用程序,因为 GAE 运行的构建过程没有将它们转移进来。相反,我需要:

  • 制作多个 app.yaml 文件(在我的例子中是 app-staging.yaml 和 app-prod.yaml)
  • 更新 .circleci/config.yml 以在每个命令语句中使用它们,例如:

    命令:gcloud app deploy app-staging.yaml

【讨论】:

    【解决方案2】:

    尝试在 docker: 部分中指定变量。

    docker:
        environment:
            ENV_ROLE: development
    

    这应该使用环境变量启动您的容器。在我的容器可以访问之前,我必须测试在几个构建中插入 VAR 的位置。

    如果您可以在需要 ENV_ROLE 的地方看到这些变量中的任何一个,那么您可能还想在此处添加。

    environment:
              DATABASE_URL: ...
            environment:
              POSTGRES_USER: ...
              POSTGRES_DB: ...
    

    【讨论】:

      猜你喜欢
      • 1970-01-01
      • 1970-01-01
      • 2013-10-16
      • 2021-11-09
      • 2016-10-27
      • 2020-10-07
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      相关资源
      最近更新 更多