Jenkins deploy hook on push / merge, adapting pom.xml going cyclic

Question

In Jenkins, we want to implement a hook on push (merge) to the Git master (GitHub). The goal of this hook is updating the pom.xml.

The problem that we envision is that we would create cyclic process. Updating a pom.xml is a new push (merge), which triggers the hook, which updates the pom.xml etc.

Is there a solution out there that solves this issue?

Answer 1

The solution (do not commit to master but to a separate tag) is described here.