Hi,

Thank you for your answers. 
I had the possibility to build the project but I noticed the local branch 
is pushed and the release is done in this branch instead of the master. 
I tryed using "master" as local branch but I get this error message : Ref 
master already exists
Just a small info which may be important: I work on an old Hudson, I don't 
have the possibility to move to Jenkins (yet)

Is there a way to work in the master ?

I'm a bit lost ;)

On Monday, July 15, 2013 7:02:47 PM UTC+2, Frédéric Bouquet wrote:
>
> Hi,
>
> Just passed to git, I've moved some of my projects from SVN to GIT. In 
> Jenkins, builds are working but when I try to release, I get the following 
> stack trace (see at the end of this mail).
>
> I configured a very simple project here : 
> https://github.com/bouquetf/test-git-release-plugin
> I reprodued the issue on dev@cloud (cloudbees). For the configuration, 
> it's quiet simple : maven-release-plugin, basic configuration for the rest 
> of the project.
>
> I tryed several possibilities : 
> - merge origin and master after pull : does not work
> - create a branch at each pull : works for only one build. After, sir 
> Jenkins says the branch already exists.
>
> Of course, searching the internet did not help much.
>
> Hope you'll have an idea to help me.
>
> Here's the stacktrace : 
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare 
> (default-cli) on project test-release-plugin: An error is occurred in the 
> checkin process: Exception while executing SCM command.
>
>       at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
>       at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>       at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>       at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>       at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>       at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>       at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>       at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>       at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>       at 
> org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>       at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>       at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>       at java.lang.reflect.Method.invoke(Method.java:606)
>       at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
>       at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
>       at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
>       at hudson.maven.Maven3Builder.call(Maven3Builder.java:100)
>       at hudson.maven.Maven3Builder.call(Maven3Builder.java:66)
>       at hudson.remoting.UserRequest.perform(UserRequest.java:118)
>       at hudson.remoting.UserRequest.perform(UserRequest.java:48)
>       at hudson.remoting.Request$2.run(Request.java:326)
>       at 
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
>       at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>       at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>       at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>       at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>       at java.lang.Thread.run(Thread.java:724)
> Caused by: org.apache.maven.plugin.MojoExecutionException: An error is 
> occurred in the checkin process: Exception while executing SCM command.
>       at 
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:281)
>       at 
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:232)
>       at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>       at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>       ... 27 more
> Caused by: org.apache.maven.shared.release.ReleaseExecutionException: An 
> error is occurred in the checkin process: Exception while executing SCM 
> command.
>       at 
> org.apache.maven.shared.release.phase.AbstractScmCommitPhase.checkin(AbstractScmCommitPhase.java:160)
>       at 
> org.apache.maven.shared.release.phase.AbstractScmCommitPhase.performCheckins(AbstractScmCommitPhase.java:145)
>       at 
> org.apache.maven.shared.release.phase.ScmCommitPreparationPhase.runLogic(ScmCommitPreparationPhase.java:76)
>       at 
> org.apache.maven.shared.release.phase.AbstractScmCommitPhase.execute(AbstractScmCommitPhase.java:78)
>       at 
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:234)
>       at 
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:169)
>       at 
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:146)
>       at 
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:107)
>       at 
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:277)
>       ... 30 more
> Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM 
> command.
>       at 
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63)
>       at 
> org.apache.maven.scm.provider.git.AbstractGitScmProvider.executeCommand(AbstractGitScmProvider.java:291)
>       at 
> org.apache.maven.scm.provider.git.AbstractGitScmProvider.checkin(AbstractGitScmProvider.java:217)
>       at 
> org.apache.maven.scm.provider.AbstractScmProvider.checkIn(AbstractScmProvider.java:410)
>       at 
> org.apache.maven.shared.release.phase.AbstractScmCommitPhase.checkin(AbstractScmCommitPhase.java:156)
>       ... 38 more
> Caused by: org.apache.maven.scm.ScmException: Detecting the current branch 
> failed: fatal: ref HEAD is not a symbolic ref
>
>       at 
> org.apache.maven.scm.provider.git.gitexe.command.branch.GitBranchCommand.getCurrentBranch(GitBranchCommand.java:147)
>       at 
> org.apache.maven.scm.provider.git.gitexe.command.checkin.GitCheckInCommand.createPushCommandLine(GitCheckInCommand.java:192)
>       at 
> org.apache.maven.scm.provider.git.gitexe.command.checkin.GitCheckInCommand.executeCheckInCommand(GitCheckInCommand.java:132)
>       at 
> org.apache.maven.scm.command.checkin.AbstractCheckInCommand.executeCommand(AbstractCheckInCommand.java:54)
>       at 
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
>       ... 42 more
>
>
>
> Thank you
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to