TeamCity and Maven2 runner

What is the intent of the 'Build number format' and "Build counter' build configurations with respect to Maven2 runners? The actual build number of the maven2 project is specified in the pom.xml file so what purpose do these entries serve?

How do I configure the Build Configuration page to release an artifact that is currently at version 1.5-SNAPSHOT? (In this case it will generate the 1.5 release.)

How do I configure the Build Configuration page to deploy another build of 1.5-SNAPSHOT? (In this case the build name is still 1.5-SNAPSHOT but it's time/date is different.)

I don't see how TeamCity is designed to work with maven2. Is there some user docs on how to do this?

2 comments
Comment actions Permalink

What is the intent of the 'Build number format' and "Build counter' build configurations with respect to Maven2 runners? The
actual build number of the maven2 project is specified in the pom.xml file so what purpose do these entries serve?

>

Yes, these are not suitable for maven projects themselves, though they are used by TeamCity to present the history of your build
configuration on the server (just like for other configurations)

How do I configure the Build Configuration page to release an artifact that is currently at version 1.5-SNAPSHOT? (In this case
it will generate the 1.5 release.)

>

How do I configure the Build Configuration page to deploy another build of 1.5-SNAPSHOT? (In this case the build name is still
1.5-SNAPSHOT but it's time/date is different.)

>

This is configured in Maven's pom.xml and Maven takes care of versioning and deployment. What would you like the server to do with
the artifacts from Maven's repository?

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

I would like TeamCity to display the real version of the artifact it is building, and this is specified in the pom.xml file. I don't see any value in the TeamCity build numbers. The only possible issue/problem I can see with displaying the maven version is the case where you are building a snapshot; in this case the version does not change. However, in this case I think maven stores a timestamp in the metadata and this could be the ideal way to distinguish between snapshot versions.

-dh

0

Please sign in to leave a comment.