bundle command changes phase to public and probably shouldn't

[Pierre-Yves David]

On Thu, Sep 27, 2012 at 10:26:38AM -0600, Ethan Barnes wrote:
> In our workflow we have a build server that builds our potential fixes 
> on multiple platforms. A custom extension bundles our changeset(s) up 
> and sends them to the build server. When an error is found, we correct 
> it locally then resubmit to the build server. This may happen several 
> times before a changeset is actually pushed to the master repo.
> 
> The problem is that every time we submit to the build server, the bundle 
> command makes the changes public. Thus, when attempting to correct 
> errors found by the build server, the phase is always "wrong".

No, it doesn't. "hg bundle" creates bundle without phase data
and do not change any phase locally (I just checked to be sure)

I think you have another operation in you script that make either push
or a pull operation with the build server. This exchange turns your
changeset public (as they are seen on a public server).

You should either (A) remove this push/pull step (B) make your build
server non publishing.

If this assumption is False, I would like to seen your custom extension
code.

> This e-mail (and any attachments) is confidential and may be
> privileged.  Any unauthorized use, copying, disclosure or
> dissemination of this communication is prohibited.  If you are not the
> intended recipient,  please notify the sender immediately and delete
> all copies of the message and its attachments.

This confidential e-mail have been sent to a public mailing list (I
know, that's not your fault)

-- 
Pierre-Yves David

http://www.logilab.fr/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20120928/3c257929/attachment.asc>