Invalid git authentication does not fail build about git

[jfairley]

My configuration of this plugin is as follows:

    ['@semantic-release/git', {
      assets: ['pom.xml']
    }],

(I'm releasing a maven project.)

---

My semantic-release dependencies are

    "@semantic-release/exec": "3.3.0",
    "@semantic-release/git": "7.0.7",
    "semantic-release": "15.12.5"

[pvdlg]

semantic-release first attempt to the git push --dry-run without using any token you might have configured, and if that fails tried again with the token.
This is what happened here. The failure message you see is due to the first attempt without the token and continued because the second attempt worked.

I don't know why it failed later though as you didn't provide the full logs.

[jfairley]

Ok, this makes sense. My build failed later, because I tried to do git push with the @semantic-release/exec plugin.

I'm using CircleCI, and I've just applied a "user SSH key" to my repo, and I no longer get the error I showed in the description. I presume that also means that my manual push will work too, but I don't have a release to make right now. I'll try it next time.

If you happen know the command line pattern for pushing with a specified token, could you paste it? ... I know, you use node libraries in the tool, so no problem if you don't know it off-hand. I'm sure this is the right path.

[pvdlg]

The best is to not use @sematnic-release/exec to make that push and to use semantic-release/git which is meant for that.
I'm going to close this issue ass it seems everything works ass expected.

[jfairley]

@pvdlg I understand and agree with your suggestion, and I would if it worked that way.

I'm releasing a maven project and the common paradigm is:

1. Increment the version and commit pom.xml.
   • This represents going from x.y.z-SNAPSHOT to ${nextRelease.version}.
   • This is a perfect "prepare" phase and fits well into @semantic-release/git.
   • This is also the commit that gets tagged by the semantic-release core library.
2. Build and deploy the Java artifacts.
   • This is a perfect "publish" phase. Still looking good.
3. Increment the version and commit pom.xml.
   • This represents going from ${nextRelease.version} back to a snapshot version (some increment of that "next" version, patch increment for me).
   • There is nothing I have found in semantic-release that fits this phase, so I'm using @semantic-release/exec and doing it during the "success" phase.

Even the maven-semantic-release plugin linked from the main docs does this extra stuff. In his case, it's attached to the "publish" phase, but 6-half-dozen.
https://github.com/conveyal/maven-semantic-release/blob/dev/lib/publish.js

---

If at least the @semantic-release/git plugin executed the git push during the "publish" phase rather than "prepare", I could work with that and wouldn't have to write my own git push command, but as-is, it's just too soon.

[jfairley]

Kinda strange to execute a git push during "prepare" IMO, when I really think about it.

[jfairley]

I guess there's this... #117

😦