Buildpack logs to STDERR when doing normal operations about ruby-buildpack

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/84963100.

[jchesterpivotal]

This behaviour comes from git, which loves to spray status updates into STDERR. See for example this discussion.

I'm personally wary of tinkering with the git defaults, but I also hate spurious errors. I don't consider this bug, we might reschedule it as a story.

[jchesterpivotal]

We've scheduled a story to change Git's behaviour to only show up on STDOUT. I'll close this issue once we're done.

[emalm]

Is the DEA's buildpack runner the code actually performing the git clone here? https://github.com/cloudfoundry/dea_ng/blob/master/buildpacks/lib/git.rb

What's the cf push command used to push this app? Does it specify a buildpack?

[pivotal-feedback]

The buildpack is not explicitly specified as part of the push command, but
it is implicitly specified (to ruby-buildpack v1.1.3 in our case) due to
the way CF caches buildpacks.

~Will
Engineering Manager
Pivotal Labs

On Wed, Dec 24, 2014 at 10:13 AM, Eric Malm [email protected]
wrote:

Is the DEA's buildpack runner the code actually performing the git clone
here?
https://github.com/cloudfoundry/dea_ng/blob/master/buildpacks/lib/git.rb

What's the cf push command used to push this app? Does it specify a
buildpack?

—
Reply to this email directly or view it on GitHub
https://github.com/cloudfoundry/ruby-buildpack/issues/27#issuecomment-68067630
.

[squeedee]

New story in Buildpacks backlog: https://www.pivotaltracker.com/n/projects/1042066/stories/85124412

[Dannyzen]

This story was completed and this is good to close