Cannot say, why it is so, but I agree that it feels like a bug.
I had no luck to get the M2 Release Plugin working with the git plugin at all - even after following several advises found by googling for the problem. I have now a freestyle job which does
git clone repo; mvn release:prepare release:perform Why is the git plugin making that so difficult? Christoph Am 21.07.2013 08:45, schrieb domi:
Hi everyone, is there a specific reason why the git-plugin does not checkout or change to an active branch? When I go to the workspace and check the git status, it tells me that we currently do not stay on any branch: elongatus:free domi$ *git status* *# Not currently on any branch.* nothing to commit (working directory clean) elongatus:free domi$ *git branch* ** (no branch)* master Because of this, In every job I have to do this to stay on a real branch, otherwise the maven-release-plguin will not be able to do a release build. git checkout master || git checkout -b master git reset --hard origin/master So to me this feels more like a bug, but maybe there is a reason behind this? /Domi -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
-- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
