Build fails with "Unable to select a buildpack"

[olalonde]

Steps to reproduce

git clone https://github.com/RocketChat/Rocket.Chat.git
cd Rocket.Chat
deis create rocket
deis config:set BUILDPACK_URL=https://github.com/RocketChat/heroku-buildpack-meteor
# also tested
# deis config:set BUILDPACK_URL=https://github.com/RocketChat/heroku-buildpack-meteor.git
git push deis

$ kd logs rocket-git-465797e7
-----> Unable to select a buildpack

Additionally, any subsequent git push will fail unless rocket-git-465797e7 is manually deleted with kd delete pod rocket-git-465797e7 and the builder restarted with kd delete pod deis-builder-4bvr5 (or kd delete pod $(kd get pods | grep deis-builder | cut -f 1 -d " ")).

[olalonde]

Might be related to #123 (environment variables not available during build)

[bacongobbler]

Yes that sounds very relevant. BUILDPACK_URL is fetched during the build IIRC. I tested custom buildpacks earlier and they worked last week so maybe something recent broke it.

[arschles]

@bacongobbler @olalonde looks like it regressed, as I tested custom buildpacks last week and they worked as well. Will look at it this week and add a test once it's fixed.

[arschles]

@olalonde if you run builder with DEBUG=1, do you see a line like found custom buildpack URL xyz?

[olalonde]

@arschles do you mean DEBUG=1 git push deis?

[olalonde]

FWIW, it seems the buildpack I was trying to use doesn't work on CoreOS/docker anyways... maybe that's what was causing the problem? coreos/bugs#1095

[bacongobbler]

That doesn't seem to be the problem. If we hit that issue, the buildpack wouldve been fetched and you wouldve seen log output from the build.

[arschles]

@olalonde sorry, I meant running the builder Replication Controller with DEBUG set to "1" in the environment variables. You'd add the following under the env: section in the yaml:

- name: DEBUG
  value: "1"

[arschles]

also, I believe what @bacongobbler says is right. The builder should start up a pod running a slugbuilder, which should be passed the custom buildpack URL in the environment. It looks like that is not happening for whatever reason.

Also, @olalonde which image tag of builder and deis/workflow are you using?

[olalonde]

I installed it using helm:

$ helm list
--->    deis (deis 2.0.0-alpha) - For testing only!
--->    deis-lite (deis-lite 2.0.0-alpha) - For testing only!

[bacongobbler]

@olalonde would you mind trying the following off master?

First, you'll need to install Helm v0.3, then run the following

helm uninstall deis
helm update
helm generate deis-dev
helm install deis-dev

Then try again and verify if you're seeing this on master. It's possible that this was fixed recently (2.0-alpha was released before New Year's, so in terms of velocity for 2.0-stable it's ancient) ;)

[olalonde]

@bacongobbler yes happy to do so, just wasn't sure how to do it 👍

[smothiki]

@olalonde are you still facing the issue.

[olalonde]

Oh sorry, didn't have time to test... Guess you can close the issue and I'll comment here if it still fails when I have time to test it!

[arschles]

Thanks @olalonde. Closing