Re: Request for Multibuildpack Use Cases

Dubois, Jan <jan.dubois@...>

The problem right now is that the buildpack names are no longer available during staging. All the code is available (because the stager needs to call `bin/detect` for each buildpack in turn), but it uses a hash as the directory name.

I made a quick experiment that grabs the mapping from buildpack names to filesystem location directly out of the CCDB and stuffs it into a CF_BUILDPACKS environment variable. With that in place, it is a trivial change to extend the multi-buildpack to support admin buildpacks as well. I've put some more information into the

I haven't tested this with the legacy DEA; I only checked it with Diego.

I would be happy to work on patches for CC and Stager to implement support for CF_BUILDPACKS if this approach is considered useful by the community, and acceptable to buildpack team.

Please let me know what you think about this approach!


From: Jack Cai <greensight(a)<mailto:greensight(a)>>
Reply-To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)<mailto:cf-dev(a)>>
Date: Tuesday, April 12, 2016 at 9:36
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)<mailto:cf-dev(a)>>
Subject: [cf-dev] Re: Re: Request for Multibuildpack Use Cases

It would be more useful if the multi-buildpack can reference an admin buildpack in addition to a remote git-hosted buildpack. :-)


On Tue, Apr 12, 2016 at 6:38 AM, David Illsley <davidillsley(a)<mailto:davidillsley(a)>> wrote:
In the past we've used the multi-buildpack to be able to use ruby sass to compile SCSS for non-ruby projects (node and Java). In that case we used the multi-buildpack and a .buildpacks file which worked reasonably well (and was very clear).

On Mon, Apr 11, 2016 at 1:15 AM, Danny Rosen <drosen(a)<mailto:drosen(a)>> wrote:
Hi there,

The CF Buildpacks team is considering taking on a line of work to provide more formal support for multibuildpacks. Before we start, we would be interested in learning if any community users have compelling use cases they could share with us.

For more information on multibuildpacks, see Heroku's documentation [1]

[1] -

Join { to automatically receive all group messages.