On Thu 16 Nov 2017 at 21:10, Adam Hardy
wrote:
> On 16/11/17 20:40, Stephen Connolly wrote:
> > I think you’ll want to keep master with a version of at least SNAPSHOT or
> > 1-SNAPSHOT and wholesale replace it with the real build version number on
> > the CI server
On 16/11/17 20:40, Stephen Connolly wrote:
I think you’ll want to keep master with a version of at least SNAPSHOT or
1-SNAPSHOT and wholesale replace it with the real build version number on
the CI server and just have that version in the tag.
The issue with using release versions on master is
On Thu 16 Nov 2017 at 13:26, ahardy42 wrote:
> V. interesting, thanks.
>
> I'm using TeamCity so controlling an infinite loop using trigger configs
> should be easy.
>
> However I don't want to use snapshot versioning at all, so the
> maven-release-plugin is
V. interesting, thanks.
I'm using TeamCity so controlling an infinite loop using trigger configs
should be easy.
However I don't want to use snapshot versioning at all, so the
maven-release-plugin is essentially not the right tool for the job.
These projects are microservices so every code
V. interesting, thanks.
I'm using TeamCity so controlling an infinite loop using trigger configs
should be easy.
However I don't want to use snapshot versioning at all, so the
maven-release-plugin is essentially not the right tool for the job.
These projects are microservices so every code