Hudson Perforce plugin - how can I automatically update versions without restarting the build

Question

I am trying to get continuous integration using Hudson, Maven and Perforce (with scm polling used to run each build)

One requirement is to automatically update POM snapshot version numbers after each successful build.

This is trivial with the Maven release plugin, but the validation action in newer versions of POM launches yet another build, which continues indefinitely.

Is there a way to check for version updates without starting another build? There seems to be no way to exclude specific user checks, specific change lists, or specific files when the scm poll makes a rebuild decision.

This seems like a basic requirement - has been doing this for many years using Cruise Control / Ant / Perforce,

Greetings

Mark

Answer 1

I was considering switching to Hudson, but not being able to exclude certain files from the scm poll would be a transaction violation. Did you also ask this question on the Hudson mailing list?

<at>hudson <dot>dev <dot>java <dot>net users

The only workaround that I see when reading through documents seems to run assemblies based on p4 triggers, where you could then programmatically do whatever you want, but that doesn't seem like a very simple approach.

Answer 2

, Perforce . , , : POM POM. , POM .

, P4Guide.

Answer 3

, , , , . .

Answer 4

"POM"?

Hudson " Perforce" (. .) BUILD_NUMBER, Hudson, P4 .

Answer 5

, ChangeLog , . :

• RC .
• dev-, Hudson.
• , , .. .

Answer 6

​​ src. , .

• hudson . hudson , .

• script, .

• .
• pom. , [t .

, .

Answer 7

perforce . "" " ".

, , , . , , , , , . , pom.xml, , .

, :

./pom.xml
./lib/
./src/

,

//depot/project/lib/...
//depot/project/src/...

, . , , "-" , .