did always_rebuild=true in the elixir_buildpack.config solve it? (and subsequently using elixir 1.7.4)
(remember to git commit the change..)
it’s a known bug when running against elixir 1.5 Heroku Guide needs a blurb about setting the elixir version · Issue #3238 · phoenixframework/phoenix · GitHub
Made that change to no effect.
I’m deploying using pipelines which trigger on commits to master so it’s definitely in the repo.
hmm, when you check heroku run “mix --version” which heroku app are you checking against? (staging or prod?)
have you promoted the deploy.. is the build stuck on CI - can you do a manual deploy(should be a button in the interface..) - can you turn off CI..
believe there is an issue with the CI/pipeline currently.. see Support for heroku pipelines · Issue #135 · HashNuke/heroku-buildpack-elixir · GitHub
I’m not actually running any CI, just deploying. I could try taking it out of the pipeline, but I don’t know how that would fix the issue. Just seems like Heroku is running the app under the wrong elixir version.
Could you please tell more about your deplyoment process?
Is the application built and deployed into the exact same environment that is used to run it afterwards or do you have a multi stage setup where you push to staging and then heroku promotes the staging to the new production afterwards? If the latter, it might be that the promotion process is broken.
And the tip to turn of CI is, as far as I understand, only for the case that you use heroku CI to test your application before deploying it. If though you use travis or circle or some other service external to heroku, I do not think, it would make a difference.
Yup, see here: Ecto migration fails on Heroku - #6 by lukerandall
We have also updated the buildpack to use v1.5.3 by default in master.
I just went through the Phoenix Heroku deployment tutorial today, and got Elixir 1.5.0 and this error.
The buildpack seems not to be updated to 1.5.3 after all?
It worked by adding the config file.
thanks for feedback..
looks like phoenix/guides/deployment/heroku.md at main · phoenixframework/phoenix · GitHub needs to be “backported” to the 1.4 branch..
I’ve created an issue for backporting it.. "backport" heroku.md to 1.4 branch · Issue #3360 · phoenixframework/phoenix · GitHub
good question.. Have made an issue here for a new buildpack release - current release is from 2015(sic!)..
https://github.com/HashNuke/heroku-buildpack-elixir/issues/145