Repository navigation
Buildpack logs to STDERR when doing normal operations #27
Description
It's kinda scary to watch the log output as an app is deploying when there's a big red block of text. Seems like it should all go to STDOUT:
2014-12-19T16:50:57.48-0800 [STG] OUT -----> Downloaded app buildpack cache (66M)
2014-12-19T16:51:01.51-0800 [STG] ERR Cloning into '/tmp/buildpacks/ruby-buildpack'...
2014-12-19T16:51:02.84-0800 [STG] ERR Note: checking out '48a89f7ed6814cfce869bbaf9acb945baa10bd2f'.
2014-12-19T16:51:02.84-0800 [STG] ERR You are in 'detached HEAD' state. You can look around, make experimental
2014-12-19T16:51:02.84-0800 [STG] ERR changes and commit them, and you can discard any commits you make in this
2014-12-19T16:51:02.84-0800 [STG] ERR state without impacting any branches by performing another checkout.
2014-12-19T16:51:02.84-0800 [STG] ERR If you want to create a new branch to retain commits you create, you may
2014-12-19T16:51:02.84-0800 [STG] ERR do so (now or later) by using -b with the checkout command again. Example:
2014-12-19T16:51:02.84-0800 [STG] ERR git checkout -b new_branch_name
2014-12-19T16:51:03.05-0800 [STG] OUT Submodule 'buildpack-packager' (https://github.com/cf-buildpacks/buildpack-packager.git) registered for path 'buildpack-packager'
2014-12-19T16:51:03.10-0800 [STG] ERR Cloning into 'buildpack-packager'...
2014-12-19T16:51:03.38-0800 [STG] OUT Submodule path 'buildpack-packager': checked out 'fec9c4598a6496fb9fa02c288076dc120754b0b5'
Activity
cf-gitbot commentedon Dec 20, 2014
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 commentedon Dec 22, 2014
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 commentedon Dec 24, 2014
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 commentedon Dec 24, 2014
Is the DEA's buildpack runner the code actually performing the
git clonehere? https://github.com/cloudfoundry/dea_ng/blob/master/buildpacks/lib/git.rbWhat's the cf push command used to push this app? Does it specify a buildpack?
pivotal-feedback commentedon Dec 29, 2014
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 notifications@github.com
wrote:
squeedee commentedon Jan 27, 2015
New story in Buildpacks backlog: https://www.pivotaltracker.com/n/projects/1042066/stories/85124412
Dannyzen commentedon Dec 30, 2015
This story was completed and this is good to close