Error defining new ENV-VAR from command

ovnicraft · June 14, 2019, 4:19am

Hello!

i am trying to define an ENV VAR from git command, so i get this:

  - run:
      name: Set modules list to test
      command: |
        echo \'export MODULES=$(git show --name-only --format= | cut -d/ -f1 | sort | uniq | xargs | sed 's/ /,/g' | sed 's/.circleci/base/g')\' >> $BASH_ENV
        source $BASH_ENV

so i got command not found for my var, in gist all my command and error output:

gist.github.com

https://gist.github.com/ovnicraft/02f08166cc5dff6e38b846e872e4bbfa

c.yml

      - run:
          name: Set modules list to test
          command: |
            echo \'export MODULES=$(git show --name-only --format= | cut -d/ -f1 | sort | uniq | xargs | sed 's/ /,/g' | sed 's/.circleci/base/g')\' >> $BASH_ENV
            source $BASH_ENV
      - run:
          name: Run tests
          command: su - odoo -c "python ~/odoo-$ODOO_BRANCH/odoo-bin --addons-path=odoo-$ODOO_BRANCH/addons,$CIRCLE_WORKING_DIRECTORY --db_host=localhost -i $MODULES -r circleci -d odoo_$CIRCLE_BUILD_NUM --test-enable --stop-after-init"

err.txt

#!/bin/bash -eo pipefail
echo \'export MODULES=$(git show --name-only --format= | cut -d/ -f1 | sort | uniq | xargs | sed 's/ /,/g' | sed 's/.circleci/base/g')\' >> $BASH_ENV
source $BASH_ENV

/tmp/.bash_env-5d031e0e95154400085ce74a-0-build: line 1: export MODULES=base: command not found
Exited with code 127

is not clear for me why run as command if am just define de var, so i guess source $BASH_ENV is running it.

Topic		Replies	Views
Environment var from bash var Build Environment	3	820	August 28, 2018
Set environment variable from python script Build Environment	1	2464	December 11, 2020
Circleci - cannot read env variables defined inside script Build Environment	3	3832	June 18, 2018
Context env vars not being picked up inside commands Build Environment circle-yml	1	1011	July 12, 2021
Problem with setting shell environment variables that have eval in them Build Environment envars , circle-yml	2	4261	November 2, 2018

Error defining new ENV-VAR from command

Related topics