kr / heroku-buildpack-inline

Yo dawg, I heard you like buildpacks.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

no cedar-supported app detected

jpillora opened this issue · comments

Hey @kr, Any ideas?

$  tree
.
├── Procfile
└── bin
    ├── compile
    ├── detect
    ├── release
    └── run

1 directory, 5 files
$  git init
Initialized empty Git repository
$  git remote add heroku git@heroku.com:still-headland-2558.git
$  git add *
$  git commit -m 'init'
[master (root-commit) c682081] init
 5 files changed, 13 insertions(+)
 create mode 100644 Procfile
 create mode 100644 bin/compile
 create mode 100644 bin/detect
 create mode 100644 bin/release
 create mode 100644 bin/run
$  git push heroku master
Initializing repository, done.
Counting objects: 8, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (8/8), 534 bytes | 0 bytes/s, done.
Total 8 (delta 0), reused 0 (delta 0)

-----> Fetching custom git buildpack... done

 !     Push rejected, no Cedar-supported app detected

To git@heroku.com:still-headland-2558.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git@heroku.com:still-headland-2558.git'

Edit: Forgot first command:

$  heroku create -s cedar
Creating still-headland-2558... done, stack is cedar

Sorry for spam, also did:

$ heroku config:add BUILDPACK_URL=http://github.com/kr/heroku-buildpack-inline.git --app still-headland-2558
Setting config vars and restarting still-headland-2558... done, v3
BUILDPACK_URL: http://github.com/kr/heroku-buildpack-inline.git
commented

What output do you get when you push after setting BUILDPACK_URL?

What is the output of cat bin/detect and ls -l bin/detect?

I did some testing with my own build-pack yesterday and no app detected comes from the detect script failing in some way. I was confused because the echoes weren't working. Now, however, I can't get the run script to work:

jpillora ~/Code/Heroku heroku create -s cedar
Creating protected-refuge-2496... done, stack is cedar
WARNING: Incomplete credentials detected, git may not work with Heroku. Run `heroku login` to update your credentials. See documentation for details: https://devcenter.heroku.com/articles/http-git#authentication
jpillora ~/Code/Heroku git clone git@heroku.com:protected-refuge-2496.git
Cloning into 'protected-refuge-2496'...
Initializing repository, done.
warning: You appear to have cloned an empty repository.
Checking connectivity... done.
jpillora ~/Code/Heroku cd protected-refuge-2496/
jpillora ~/Code/Heroku/protected-refuge-2496 heroku config:add BUILDPACK_URL=http://github.com/kr/heroku-buildpack-inline.git
Setting config vars and restarting protected-refuge-2496... done, v3
BUILDPACK_URL: http://github.com/kr/heroku-buildpack-inline.git
jpillora ~/Code/Heroku/protected-refuge-2496 echo "work: bin/run" > Procfile
jpillora ~/Code/Heroku/protected-refuge-2496 mkdir bin
jpillora ~/Code/Heroku/protected-refuge-2496 echo "#!/bin/sh
                                             echo Test
                                             " > bin/detect
jpillora ~/Code/Heroku/protected-refuge-2496 echo "#!/bin/sh
                                             echo Compiled
                                             " > bin/compile
jpillora ~/Code/Heroku/protected-refuge-2496 echo "#!/bin/sh
                                             echo Running
                                             " > bin/run
jpillora ~/Code/Heroku/protected-refuge-2496 echo "#!/bin/sh

                                             cat << EOF
                                             ---
                                             EOF" > bin/release
jpillora ~/Code/Heroku/protected-refuge-2496 chmod +x bin/
bin/compile  bin/detect  bin/release  bin/run
jpillora ~/Code/Heroku/protected-refuge-2496 chmod +x bin/*
jpillora ~/Code/Heroku/protected-refuge-2496 tree
.
├── Procfile
└── bin
    ├── compile
    ├── detect
    ├── release
    └── run

1 directory, 5 files
jpillora ~/Code/Heroku/protected-refuge-2496 git add *
jpillora ~/Code/Heroku/protected-refuge-2496 git commit -m init
[master (root-commit) c2309ef] init
 5 files changed, 15 insertions(+)
 create mode 100644 Procfile
 create mode 100755 bin/compile
 create mode 100755 bin/detect
 create mode 100755 bin/release
 create mode 100755 bin/run
jpillora ~/Code/Heroku/protected-refuge-2496 git push
Initializing repository, done.
Counting objects: 8, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (8/8), 521 bytes | 0 bytes/s, done.
Total 8 (delta 0), reused 0 (delta 0)

-----> Fetching custom git buildpack... done
-----> Test app detected
Compiled
-----> Discovering process types
       Procfile declares types -> work

-----> Compressing... done, 0K
-----> Launching... done, v4
       https://protected-refuge-2496.herokuapp.com/ deployed to Heroku

To git@heroku.com:protected-refuge-2496.git
 * [new branch]      master -> master
jpillora ~/Code/Heroku/protected-refuge-2496 heroku logs
2015-02-06T07:48:49.789617+00:00 heroku[api]: Enable Logplex by dev@jpillora.com
2015-02-06T07:48:49.789644+00:00 heroku[api]: Release v2 created by dev@jpillora.com
2015-02-06T07:49:27.806118+00:00 heroku[api]: Release v3 created by dev@jpillora.com
2015-02-06T07:49:27.806118+00:00 heroku[api]: Set BUILDPACK_URL config vars by dev@jpillora.com
2015-02-06T07:52:58+00:00 heroku[slug-compiler]: Slug compilation started
2015-02-06T07:53:21.056890+00:00 heroku[api]: Deploy c2309ef by dev@jpillora.com
2015-02-06T07:53:21.056890+00:00 heroku[api]: Release v4 created by dev@jpillora.com

bin/run has #!/bin/sh echo Running logs should say "Running" right?