Mike, this is so buildpacks can be composed together. For example, if a user want to use NodeJS to compile Javascript assets for a Java app (yes, there always Maven support, but some have different

Orchestrating a raft cluster in a way that requires no manual intervention is incredibly difficult. We write the PID file late for a specific

Thanks! This was happening in JBP v3.3.1, I just tested with JBPv 3.6 and it's working.

Finally got around to testing this. Preliminary testing show that "\u2028" doesn't function as a new line character in bash and causes eclipse console to wig out. I don't think "\u2028" is a viable

Hi all, The buildpacks team would like to propose a change to the nodejs buildpack. It was recently brought to our attention in this

An interesting proposal. Any thoughts about this proposal in relation to multi-buildpacks [0]? How many of the use cases for this feature go away in lue of multi-buildpack support? I think it would

This seems to be yet another way to extend buildpacks with out forking to go along with [0] and [1]. My only hope is that all these newly proposed extension mechanisms come together in a simple,

Actually, doing some further tests, I realize a mere 'join' is definitely not enough. Instead, you need to restore the raft/peers.json on each one of the 3 consul server nodes: monit stop

Very neat! Thanks a lot Eric.

Hi cf devs, I’m running a CF deployment with redundancy, and I just experienced my consul servers not being able to elect any leader. That’s a VERY frustrating situation that keeps the whole CF

Hi, Benjamin, Yes, the BOSH-Lite boxes with kernel 3.19.0-40 through 3.19.0-50 are all susceptible to the AUFS bug. Kernel versions 3.19.0-51 and later will be fine, and I believe the earliest

Hi, Sorry for the late up, but would this hit bosh-lite too? Because after it has run for a while, I’m experiencing severe similar issues with the 53 garden containers I use in Bosh-Lite. Config

Hello, According to code https://github.com/cloudfoundry-incubator/nsync/blob/01a624d23cb683f35c88c4160205c4ad880faaf0/recipebuilder/recipe_builder.go#L72-L84 , diego apps scale the number of

All buildpacks except the binary buildpack perform build at push time. Both "buildpacks" and "12-factor" came out of Heroku. That said, whether to use the Go buildpack vs binary buildpack is

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

Buildbacks are still environmentally aware of the target build environment. They mean you don't need to worry about cross platform support. wrote:

On a lazy sunday evening experimenting with the Go and Binary buildpacks, a thought came to my head regarding cloud native patterns, and in particular 12 factors' Build, Release, Run. To me, the Go

Thank you, Eric. The query into auth_username and password, prompted me to review the manifest. Those were not correct and a typo in the cc_uploader, cc, base_url. I've made the corrections. I likely

Thanks, Tom. The errors about the 401 response code make me suspect that the nsync-bulker doesn't have the correct basic-auth credentials for the internal app-enumeration endpoint it queries on CC.

Yes, the logs are there. I grepped the logs for error. I see a lot