# CircleCI 2.0 does not support environment variables that refer to each other the same way as 1.0 did. Working_directory: ~/FoundersPledge/founders-pledge # cases it should duplicate the execution of your original 1.0 config. # configuration as a reference rather than using it in production, though in most In general, we recommend using this generated # for configuration has changed substantially in 2.0 to allow arbitrary jobs rather # comments in this file to understand the structure of CircleCI 2.0, as the idiom # It should include any build commands you had along with commands that CircleCI circleci/config.yml This configuration was automatically generated from a CircleCI 1.0 config. RUN bundle exec rake assets:precompile -trace RUN bundle install -without development test -jobs 4 -retry 3ĮNV DATABASE_URL postgresql://localhost/dummy_url Contents of various plausibly relevant files follow:įROM ruby:2.6.5-alpine RUN apk add -update -no-cache \ I really have no idea how to proceed here, so I’ll cross post this on the Convox and Circle forums, and see if anyone can identify what’s happening. I feel like this has to be either a CircleCI or a Convox issue, but I can’t tell which - the tests run fine on Circle, which seems to prove that it’s picking up the env var there (and therefore ‘must’ be a Convox issue), but running the exact same command line command from my local terminal ( convox deploy -app founderspledge-staging) deploys it ok, which seems to ‘prove’ it’s a Circle issue. I have quadruple-checked that the variable is present on both, and tried refreshing it multiple times.
I had not originally touched the previous credentials, which were set in the RAILS_MASTER_KEY env var on both CircleCI and Convox, and which were working throughout before the upgrade from 5.1.
Ask your team for your master key and write it to /app/config/master.key or put it in the ENV. Missing encryption key to decrypt file with. In the development environment everything (eventually) worked ok, and the tests passed on Circle CI, but then hit a pernicious bug when I came to deploy it to our staging environment: I’ve recently been attempting to upgrade our app from Rails 5.1 to 6.0.0.
0 kommentar(er)
