HashNuke / HashNuke/heroku-buildpack-elixir
erl not available in Heroku CI debug shell
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 812
- Forks
- 329
- PR merge metrics
- No merged PRs in 30d
Description
To reproduce
git clone https://github.com/HashNuke/heroku-buildpack-elixir-test.gitcd heroku-buildpack-elixir-test- Add the following
app.jsonfile:
{
"name": "buildpack-test",
"scripts": {},
"env": {},
"formation": {},
"addons": [
{
"plan": "heroku-postgresql"
}
],
"buildpacks": [
{ "url": "https://github.com/HashNuke/heroku-buildpack-elixir.git" }
]
}
git add app.jsongit commit -m "Add app.json"heroku create --buildpack "https://github.com/HashNuke/heroku-buildpack-elixir.git"git push heroku master(not sure if needed)- Create a Github repo and associate it to the CI of your new Heroku app.
git push origin mastershould trigger the test runner.heroku ci:debug --pipeline [pipeline-name]- In the remote prompt:
erl
Current behavior
bash: erl: command not found
Expected behavior
- Erlang shell should start
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue using the listed Heroku CI commands and the app.json configuration, then enter the debug shell and run erl. Trace the buildpack's installed runtime commands and verify that the Erlang shell is available in the debug environment; done means erl starts successfully there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, erlang, shell
- Domain
- build-system, cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100