Re: Special parameters - sha1

Hello, If you have a POM with dependencies to other modules which are built on each change, you typically want to make sure you use those updated dependencies when you compile your projects. With regularly changing version numbers and without using SNAPSHOT dependencies you will need to find

Re: Special parameters - sha1

I'm not sure what you mean when you say: "How are you planning to deal with the changed version numbers of dependencies?" At which stage are you referring to? Which dependencies with changed version numbers? Thanks, Eric On Wed, Nov 15, 2017 at 1:11 AM, Bernd Eckenfels

Re: Auto-increment semantic version number for CD pipeline with git and docker

I'm using TeamCity so controlling an infinite loop using trigger configs should be easy. I don't want to use snapshot versioning at all. These projects are microservices so every code commit is a release candidate. My goal is to get maven to increment the build number on each build - the build

Re: Auto-increment semantic version number for CD pipeline with git and docker

On Wed 15 Nov 2017 at 18:11, Arnaud bourree wrote: > Hi, > > I like your blog post, but I need some clarification. > > On line 19, your pipeline snippet calls maven without goals ! > 1/ Does it means: release:prepare goal? The line is very long, scroll horizontally

Re: Auto-increment semantic version number for CD pipeline with git and docker

Hi, I like your blog post, but I need some clarification. On line 19, your pipeline snippet calls maven without goals ! 1/ Does it means: release:prepare goal? 2/ In your idea, do we add our project maven build lines before line 22? I order to take decision after some automatic tests validation.