Using Pipelines for continuous delivery with semantic versioning and git-flow

[Deleted user]

Hi everyone,

We're using git-flow and have separate development and a master branch for staging/production code.

When a commit is made to development it triggers a build that bumps the version number and commits it to the repository. This commit in turn triggers a new build, so on and so forth.

Is there a recommended approach to configure continuous delivery using the above set up? 

Thanks.

[mwatson · Accepted solution]

We'd probably need more details of your intended setup of branches and what you're trying to achieve to have a definitive answer.

However what you don't want to do is have builds that commit back trigger more builds that commit back - you should configure your tools to add "[skip ci]" to the commit message as mentioned in our FAQ so that this is avoided.

Let us know if this is the answer you were looking for or there was more you wanted to know.