Pass BUILDPACK_URL variable to herokuish in Auto DevOps template

In Auto DevOps template, we want to support BUILDPACK_URL variable to specify a specific buildpack.

This behavior is supported by herokuish, but we don't pass the variable correctly when invoking it.

We should pass the variable in https://gitlab.com/gitlab-org/gitlab-ci-yml/blob/master/Auto-DevOps.gitlab-ci.yml#L511.

### Summary We have auto dev ops up and running successfully on our kubernetes cluster. It's worked great so far except today we tried to use it for a dotnet core project...

We get:

...
a1ed5cb6c6de: Pull complete
c83c23d03477: Pull complete
Digest: sha256:f8699550a58b928b2f273afc04466298e8a970ecd86c81f6dc3e5e05944f7db5
Status: Downloaded newer image for gliderlabs/herokuish:latest
       -----> Unable to select a buildpack
ERROR: Job failed: error executing remote command: command terminated with non-zero exit code: Error executing in Docker Container: 1

Following the instructions here we set the BUILDPACK_URL in the Settings->CI/CD->Secret variables to the buildpack URL "https://github.com/jincod/dotnetcore-buildpack" which is the most recommended buildpack at the moment for dotnet core.

Unfortunately that yielded no difference.

So we added a .buildpack file to the repo... Same result.

Are we missing a step? Is the URL bad in some way? Does this actually work?

Steps to reproduce

See above. The dotnet core project is a basic hello world project.

Example Project

hello.tar.gz

What is the current bug behavior?

The build starts and ultimately hits the error as shown above.

What is the expected correct behavior?

It should use the buildpack specified in the project variable or .buildpack file.

Results of GitLab environment info

Expand for output related to GitLab environment info 
System information
System:         Debian 8.9
Proxy:          no
Current User:   git
Using RVM:      no
Ruby Version:   2.3.5p376
Gem Version:    2.6.13
Bundler Version:1.13.7
Rake Version:   12.0.0
Redis Version:  3.2.5
Git Version:    2.13.5
Sidekiq Version:5.0.4
Go Version:     unknown

GitLab information
Version:        10.0.3-ee
Revision:       eff7821
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     postgresql
DB Version:     9.6.3
URL:            omitted
HTTP Clone URL: omitted/some-group/some-project.git
SSH Clone URL:  git@omitted:some-group/some-project.git
Elasticsearch:  no
Geo:            no
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers: google_oauth2


GitLab Shell
Version:        5.9.0
Repository storage paths:
  • default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check 
Checking GitLab Shell ...

GitLab Shell version >= 5.9.0 ? ... OK (5.9.0)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
17/1 ... ok
4/2 ... ok
17/3 ... ok
2/4 ... ok
2/5 ... ok
2/6 ... ok
16/8 ... ok
15/9 ... ok
16/14 ... ok
16/17 ... ok
13/18 ... ok
16/19 ... ok
2/20 ... ok
4/23 ... ok
16/24 ... repository is empty
2/25 ... ok
22/26 ... ok
2/30 ... ok
13/31 ... ok
15/32 ... repository is empty
21/35 ... ok
21/37 ... ok
2/41 ... ok
21/42 ... ok
21/43 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK


Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful


Checking GitLab Shell ... Finished


Checking Sidekiq ...


Running? ... yes
Number of Sidekiq processes ... 1


Checking Sidekiq ... Finished


Reply by email is disabled in config/gitlab.yml
Checking LDAP ...


LDAP is disabled in config/gitlab.yml


Checking LDAP ... Finished


Checking GitLab ...


Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
17/1 ... yes
4/2 ... yes
17/3 ... yes
2/4 ... yes
2/5 ... yes
2/6 ... yes
16/8 ... yes
15/9 ... yes
16/14 ... yes
16/17 ... yes
13/18 ... yes
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
16/19 ... yes
2/20 ... yes
4/23 ... yes
16/24 ... yes
2/25 ... yes
22/26 ... yes
2/30 ... yes
13/31 ... yes
15/32 ... yes
21/35 ... yes
21/37 ... yes
2/41 ... yes
21/42 ... yes
21/43 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.3 ? ... yes (2.3.5)
Git version >= 2.7.3 ? ... yes (2.13.5)
Edited by Fabio Busatto