CONDA_BUILD_STATE not always set correctly

[bryevdv]

Attempting to update Bokeh TravisCI builds to conda-build 3.14 from 3.0.27 for bokeh/bokeh#8217 causes the Bokeh setup.py to ask for a build action interactively, stalling the build:

+conda build conda.recipe --quiet --no-test --no-anaconda-upload
Bokeh includes a JavaScript library (BokehJS) that has its own
build process. How would you like to handle BokehJS:
1) build and install fresh BokehJS
2) install last built BokehJS from bokeh/bokehjs/build
Choice? 

However, the interactive build prompt should be (and has been in previous versions) protected by a check for conda-build:

# if this is just conda-build skimming information, skip all this actual work
if not conda_rendering():
    fixup_for_packaged()   # --build_js and --install_js not valid FROM sdist
    fixup_building_sdist() # must build BokehJS when MAKING sdists

    bokehjs_action = build_or_install_bokehjs()

where conda_rendering is:

def conda_rendering():
    return os.getenv("CONDA_BUILD_STATE" ,"junk") == "RENDER"

@msarahan suggests:

seems like the load_setup_py_data may be operating in a different context somehow. The state variable stuff is tested at https://github.com/conda/conda-build/blob/master/tests/test-recipes/metadata/state_variables/meta.yaml, but that doesn't test it with loading setup.py data

[github-actions]

Hi there, thank you for your contribution!

This issue has been automatically locked because it has not had recent activity after being closed.

Please open a new issue if needed.

Thanks!