Closed alapierre closed 1 year ago
@alapierre Hello. Take a look at issue with similar error - https://github.com/aleksandr-m/gitflow-maven-plugin/issues/340. There the problem was related to git clone depth.
Great tip, thank you @aleksandr-m. I do not know the reason but on some repos Azure DevOps use --depth=1
but on some others it is not. To solve refusing to merge unrelated histories
just add in Azure pipeline definition:
variables:
- name: Agent.Source.Git.ShallowFetchDepth
value: 0
Probably this is not plugin problem, but I not know how to solve this issue.
Locally when I perform release everything works fine. But when I try to make release as an Azure Pipeline like this:
I got error in
release-finish
on merging release branchI have a lot of project with
git-flow-maven-plugin
and in all others release works perfectly on Azure DevOps.