RE: Can't get git to stop outputting to StdErr

From: Scott R. Chamberlain <srchamberlain@impromed.com>
Date: Dec 19, 2016, 14:56 UTC
Message-ID: <77ad6aeef9a245f3adeab3751e7e94eb@ES5.impromed.com>
In-Reply-To: <xmqq7f8syyhg.fsf@gitster.mtv.corp.google.com>

Microsoft fixed their git repo implementation to no longer cause this problem.

https://connect.microsoft.com/VisualStudio/feedback/details/3109654/git-host-on-visualstudio-com-does-not-respect-the-q-flag-for-pushes

Scott Chamberlain Software Engineer ImproMed, LLC (800) 925-7171 www.impromed.com

-----Original Message-----
From: Scott R. Chamberlain 
Sent: Friday, October 28, 2016 4:09 PM
To: 'Junio C Hamano' <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: RE: Can't get git to stop outputting to StdErr

This is talking to a visualstudio.com git repo. I will file a bug with them.

Scott Chamberlain Software Engineer ImproMed, LLC (800) 925-7171 www.impromed.com

-----Original Message-----
From: Junio C Hamano [mailto:gitster@pobox.com] 
Sent: Friday, October 28, 2016 4:07 PM
To: Scott R. Chamberlain <srchamberlain@impromed.com>
Cc: git@vger.kernel.org
Subject: Re: Can't get git to stop outputting to StdErr

"Scott R. Chamberlain" <srchamberlain@impromed.com> writes:

> The line I do is:
>
>     git push -q binaryRepo HEAD:"$Env:BUILD_SOURCEBRANCH"

This would

 (1) squelch the output from the sending side (i.e. local), and

 (2) ask "quiet" to the receiving side (i.e. remote), if they know
     how to be quiet.

Show 6 quoted lines

> But I get the following in my log after the build
>
>     2016-10-28T20:05:32.3179442Z ##[error]remote: 
>     remote: Analyzing objects... (3/3) (657 ms)        
>     remote: Storing packfile... done (40 ms)        
>     remote: Storing index... done (42 ms)

These three lines prefixed with "remote:" are coming from the software that runs on the remote machine that accepts your push, but the way it says these three things do not look familiar to me.  Is it possible that the remote machine is running a Git server that is not ours, which lacks the support for "quiet" capability?  If that is the case, the symptom is understandable.

A quick archive search tells me that you are seeing the same issue as this one:

https://public-inbox.org/git/20160516133731.GA6903@sigill.intra.peff.net/

where the concluding remark, to which I agree, is:

    The server side here is clearly not stock git, from the content
    of those progress messages (some googling shows it looks like
    whatever visualstudio.com is running, but I don't know what that
    is). So either the server implementation doesn't support the
    "quiet" protocol extension, or it is ignoring it. It might be
    worth filing a bug with them.

-- 
Rely On Us.
ImproMed LLC
Henry Schein Animal Health
--