Geek asks and answers

Mutual exclusive City Build team launches both firing

We have two separate assemblies configured in TeamCity for TFS with the following triggers (listed below).

Build 1:
+:Folder1/Folder2/Folder3/FilePrefix\*\*
+:Source/\*\*
+:Tests/\*\*

Build 2:
+:Folder1/Folder2/\*\*
-:Folder1/Folder2/Folder3/FilePrefix\*\*
-:Tests/\*\*
-:Source/\*\*

If we make changes to the file in Folder1/Folder2/Folder3/FilePrefix, we find that BOTH creates a trigger. The documentation states :

For each file with the change, the most specific rule was found (the rule corresponding to the long path to the file). The assembly starts if there is less than one file with the corresponding "include" rule or with a file without a matching rule.

Does this not mean that only a priority rule has priority? Why is there no assembly 2 excluding this file due to -:Folder1/Folder2/Folder3/FilePrefix**? It seems to +:Folder1/Folder2/**override the ignore rule.

+5
1

, '.' "*" .

, build2 :

+:Folder1/Folder2/\*\.
-:Folder1/Folder2/Folder3/FilePrefix\*\.
-:Tests/\*\.
-:Source/\*\.
+1

More articles:


All Articles