Git development
 help / color / mirror / Atom feed
From: "Scott R. Chamberlain" <srchamberlain@impromed.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Can't get git to stop outputting to StdErr
Date: Fri, 28 Oct 2016 20:31:02 +0000	[thread overview]
Message-ID: <c09d32d8ab97418d98ddf356e20a6ff5@ES4.impromed.com> (raw)

I am working on some build scripts that get run on TFS. During the build process I need to check in the changes that where done during the build process (A set of binaries other projects depend on).

I would really like to leave the option "Fail on Standard Error" enabled for the script in TFS, however my push keeps writing to standard error even though I told it not to.

The line I do is:

    git push -q binaryRepo HEAD:"$Env:BUILD_SOURCEBRANCH"

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)        
    
    2016-10-28T20:05:32.3209423Z Done
    2016-10-28T20:05:32.4019436Z ##[error]Process completed with exit code 0 and had 1 error(s) written to the error stream.
    2016-10-28T20:05:32.4029436Z ##[debug]System.Exception: Process completed with exit code 0 and had 1 error(s) written to the error stream.

Why am I still getting output to standard error when I included the `-q` switch?

For reference, `git version` reports `2.10.0.windows.1` and HEAD is a detached HEAD.


Scott Chamberlain
Software Engineer 
ImproMed, LLC



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


             reply	other threads:[~2016-10-28 20:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28 20:31 Scott R. Chamberlain [this message]
2016-10-28 21:06 ` Can't get git to stop outputting to StdErr Junio C Hamano
2016-10-28 21:08   ` Scott R. Chamberlain
2016-12-19 14:56   ` Scott R. Chamberlain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c09d32d8ab97418d98ddf356e20a6ff5@ES4.impromed.com \
    --to=srchamberlain@impromed.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox