[Bug 4383] New: Allow more control of Mercurial prompt behavior when running non-interactively

mercurial-bugs at selenic.com mercurial-bugs at selenic.com
Tue Sep 23 16:49:56 CDT 2014


http://bz.selenic.com/show_bug.cgi?id=4383

          Priority: normal
            Bug ID: 4383
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: Allow more control of Mercurial prompt behavior when
                    running non-interactively
          Severity: feature
    Classification: Unclassified
                OS: Windows
          Reporter: ajensen at webmd.net
          Hardware: PC
            Status: UNCONFIRMED
           Version: 2.5.4
         Component: Mercurial
           Product: Mercurial

We have several nightly jobs that automatically check code and other resources
into our repositories. These scripts have to push changes back to the central
repository, which means handling merges. Sometimes Mercurial asks the user for
input when merging (e.g. when a file has been modified in the source branch,
but deleted in the destination branch). When there is no user to respond
Mercurial patiently waits for an answer. On a build server, running under a
Windows service, nobody is there to provide that answer. While Mercurial is
waiting, no other builds can run, and eventually our build server kills
Mercurial, and a mess is left behind in the repository that we have to then go
in and clean up.

There is the --noninteractive switch, which I believe maps to the
ui.interactive config setting, but this always accepts the first answer of the
question Mercurial asks. There are some situations where we want to answer no,
but can't.

What I'd like is the ability to choose how Mercurial behaves in non-interactive
sessions: answer yes, answer no, or abort with an error. When we automate, we
can set Mercurial to abort with an error, which will free up build server
resources so that other jobs can run while a human can then deal manually with
why Mercurial aborted.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Mercurial-devel mailing list