JGitFlow maven plugin doesn't push release branch to remote

Question

I'm using jGitFlow plugin as follows:

<plugin>
    <groupId>external.atlassian.jgitflow</groupId>
    <artifactId>jgitflow-maven-plugin</artifactId>
    <version>1.0-m5.1</version>
    <configuration>
        <pushFeatures>true</pushFeatures>
        <pushReleases>true</pushReleases>
        <pushHotfixes>true</pushHotfixes>
        <noDeploy>true</noDeploy>
    </configuration>
</plugin>

When I run mvn jgitflow:feature-start and enter branch name (say testSomething) it got pushed to origin immediately. I can see that by listing branches git branch -a:

* feature/testSomething
  remotes/origin/feature/testSomething

So far so good. But now I'm doing mvn jgitflow:release-start. I enter the new version, next development version and the goal runs to completion. I'm on the newly created release branch but this branch is not pushed to remote. What I'm doing wrong? Is this intended?

Answer 1

It turned out that our git repository can be only amended via pull-requests and hence the push didn't work. It's a bit shame the plugin ignores the return value of the push and doesn't at least emit a warning.