Mark, On Tue, May 12, 2015 at 9:42 PM, Mark Payne <[email protected]> wrote: > > Well, the first 10 or so times that I tried to do "mvn release:perform", > the nifi-parent and nifi-nar-maven-plugin worked fine. For the nifi > application release, release:perform failed because it was attempting to > "batch upload" artifacts to some snapshot repository that I don't have > permissions for. > > I don't know if it's a feature of the maven release plugin or something in > the apache parent pom that I don't understand maybe? But when I named the > branch "nifi-0.1.0-incubating" and then named the SCM tag > "nifi-0.1.0-incubating-rc1" or "-rc2" or what have you, that happened. > Eventually, after many failures I found that if I name the branch > "release-nifi-0.1.0-incubating" instead, all was okay. I have no idea what > the naming of the git branch and the SCM tag have to do with each other (or > it's possible that there's something else going on that i don't understand > at all), but I just kept incrementing the RC number each time the build > failed. >
I'd say the first step would be configure the maven-release-plugin to keep local those failed tries; pushChanges=false would be the basic pillar of such strategy in combination with a local connectionUrl. This configuration I did last week could be useful: https://github.com/apache/incubator-commonsrdf/blob/master/pom.xml#L308 Hope that helps. -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 6602747925 e: [email protected] w: http://redlink.co
