[AIRFLOW-XXX] 1-setup-env.sh should only run in docker

[milton0825]

Make sure you have checked all steps below.

Jira

• My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"
  • https://issues.apache.org/jira/browse/AIRFLOW-XXX
  • In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.
  • In case you are proposing a fundamental code change, you need to create an Airflow Improvement Proposal (AIP).
  • In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Description

• Here are some details about my PR, including screenshots of any UI changes:

1-setup-env.sh should only be ran inside the docker container as it override files.

Tests

• My PR adds the following unit tests OR does not need testing for this extremely good reason:

Modified the CI bash script should not need unit test I guess?

Commits

• My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters (not including Jira issue reference)
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

Documentation

• In case of new functionality, my PR adds documentation that describes how to use it.
  • All the public functions and the classes in the PR contain docstrings that explain what it does
  • If you implement backwards incompatible changes, please leave a note in the Updating.md so we can assign it to a appropriate release

Code Quality

• Passes flake8

[milton0825]

@ashb

[potiuk]

It's really good idea. I've added very similar solution to my WIP PR for multi-staging. The nice thing there is that the image to run CI is part of airflow itself and we already had a few ENV variables defined that we could use.

#4938 (but I added it in all scripts that are run in the container - there are a few places to add it: 9a94899#diff-9cf9f4241b4e721774c938abb1c6c103R25

[feng-tao]

lgtm

[milton0825]

tests passed in: https://travis-ci.org/milton0825/airflow/builds/513064124