Push fails when trying to use a specific runtime version with a build pack

Products

• Services Suite

Issue/Introduction

Symptoms:

The application fails to stage, giving an error:

2014-09-24T12:35:02.53-0600 [STG] ERR Expected dependency to exist but could not find it: <url> 

Environment

Cause

When you see the error above, it means that the particular version you have specified is unknown to the buildpack.  This could be due to entering an incorrect version number or because the buildpack needs to be updated to include support for the latest version of your runtime.  Most buildpacks, like the Ruby, Go or Python build packs, need to be updated to support new versions of their respective runtimes.  

These updates may take a little time to become available in the default list of buildpacks on PWS. 

Resolution

If you encounter this problem, you can often work around the issue by simply using a specific buildpack instead of relying on the default included with PWS.  You can do this by adding the -b argument to your cf push command or by adding the buildpack attribute into your manifest.yml file, and indicating the URL of the buildpack you'd like to use.

Ex: cf cli

cf push -b https://github.com/my/buildpack#v<version>

Ex: manifest.yml

---
applications:
- name: app-name
  memory: 128M
  instances: 1
  path: .
  buildpack: https://github.com/my/buildpack#v<version>

Here is a link to the page of supported buildpacks on PWS:

• Ruby
• Python
• Go
• Java 
• Node.js
• PHP
• Binary
• .Net
• Node.js
• Staticfile
• NGINX
• HWC

You can also see exactly what dependencies are bundled with each buildpack here .