Jenkins: SVN trigger incorrectly sets dependencies first

Question

In Jenkins (1.550), I have two projects maven, Model and GUI. The GUI design depends on the model:

<groupId>com.acme</groupId>
<artifactId>gui</artifactId>
<version>1.0.0</version>
...
<dependencies>
    <dependency>
        <groupId>com.acme</groupId>
        <artifactId>model</artifactId>
        <version>1.0.0</version>
    </dependency>
</dependencies>

Now, for each project, I have Jenkins configured to check SVN periodically and run a build that works fine.

Problem

It works only if only files in one project are changed. Often, however, commit will be performed in both projects, so let's say that these two files will be committed:

A /model/Car.java
A /gui/CarDialog.java

, GUI , , , /model/Car.java ( ). , , (- SVN ), . gui , .

, , , - , .

, ", " , , , , SVN, .

, :

SVN 4 :

*/4 * * * *

GUI SVN 8 ​​:

*/8 * * * *

, 60 , , , .

, */4 (H/4 ) .

, ?

Answer 1

:

• Downstream-Ext Jenkins
• : gui
  • includeRegions, . : model/.*
  • " SCM"
• jenkins: master
  • includeGegions, : . .* model/.* ,gui/.*
  • "SCM "
  • : " ()"
    • : model, gui ( : ,..., )
    • tick ", SCM"
• : - Jenkins

• SCM -
• - , , , .
• - , , . - SCM, ​​ ,
• - --