Performing a Maven release with Hudson Mercurial Plugin
Matt Mackall
mpm at selenic.com
Tue May 4 14:08:06 UTC 2010
On Tue, 2010-05-04 at 10:39 +0200, Dirkjan Ochtman wrote:
> On Tue, May 4, 2010 at 10:35, Jeroen Rosenberg <jeroenr at novadoc.nl> wrote:
> > Thanks for you response. Well, the error diagnostics on stdout gave me the following message:
> >
> > abort: push creates new remote heads on branch 'default'!
> >
> > I figured that this might have something to do with having uncommitted changes made by the Hudson Mercurial Plugin which prevents me from pushing. The output from "hg status" gave me:
> >
> > ? pom.xml.releaseBackup
> > ? release.properties
> >
> > So, I added those files to my .hgignore file and committed. After I did this, I was able to push to the remote server. Now I can also perform Maven releases from Hudson without problems. Still I think this isn't a very neat solution. I also posted this on Hudson forums.
>
> The push abortion isn't related to the ignored files, but has to do
> with the fact that you likely had new csets on the server side that
> the client side hadn't seen yet.
In other words, you're missing some basic understanding of Mercurial
concepts and terminology and you're likely to be eaten by a grue. Please
take a look at the book:
http://hgbook.red-bean.com/read/a-tour-of-mercurial-merging-work.html
--
Mathematics is the supreme nostalgia of our time.
More information about the Mercurial
mailing list