Skip to content

Commit 0dc196d

Browse files
committed
Merge pull request #8 from andham/mvn3_triggers
Anders thanks for the updates
2 parents d975781 + 51b3239 commit 0dc196d

File tree

1 file changed

+16
-8
lines changed

1 file changed

+16
-8
lines changed

content/book-hudson.doc

+16-8
Original file line numberDiff line numberDiff line change
@@ -3005,18 +3005,26 @@ Build when Maven dependencies have been updated by Maven 3 integration::
30053005
send out a notification to all projects that Maven dependencies have
30063006
been updated as post build action (see
30073007
<<section-configuring-post-build-actions>>). When you activate this
3008-
build trigger a build of the project will be started once a such a
3009-
notification is received. The projects triggering each other in this
3010-
set up needs to be configured to access the same Maven repository.
3008+
build trigger, a build of the project will be started once such a
3009+
notification is received for a Maven dependency. This will create a
3010+
Upstream/Downstream Project coupling between the project producing
3011+
the Maven artifact and your project. In practice, this trigger
3012+
will only affect SNAPSHOT dependencies as releases should never change.
3013+
The projects triggering each other in this set up needs to be
3014+
configured to access the same (local or remote) Maven repository.
30113015

30123016
Build when Maven SNAPSHOT dependencies have been updated externally::
30133017

30143018
Activating this setting allows you to specify a schedule in cron
3015-
syntax to use for polling the local Maven repository for updated
3016-
SNAPSHOT dependencies. When selecting the Exclude internally
3017-
produced dependencies option the regular check will only cause a
3018-
build trigger firing when artifacts not built in a local Hudson job
3019-
are updated.
3019+
syntax to use for polling the Maven repository for updated
3020+
SNAPSHOT dependencies. The use case for this is to trigger a build
3021+
when an updated SNAPSHOT version of one of the project's Maven
3022+
dependencies has been deployed to the repository by a build outside
3023+
of the Hudson instance. The repository's URL is specified in the
3024+
global Hudson configuration. When selecting the Exclude internally
3025+
produced dependencies option, the check will only cause a build
3026+
trigger firing when artifacts not built by a project on the Hudson
3027+
instance are updated.
30203028

30213029
[[section-configuring-post-build-actions]]
30223030
==== Configuring Post-build Actions

0 commit comments

Comments
 (0)