I have looked at some other threads but they were referencing the roots wrong and said they fixed it by using the same config that I have above. The checkout rules affect the actual checkout of the sources on the agent. I have tried changing my labeling rules to the following with No success: now that the config is branches 1.1 it does not. So when the config was branches/1.0 the labeling worked. ![]() I have gotten it to work in the past but it seams that everytime we update the TC project config to checkout a new branch it runs into this problem. In case you use the server-side checkout mode, the TeamCity server sends incremental patches to. ![]() If you use the agent-side checkout mode, the build agent checks out the sources into this directory before the build. Note that exclude checkout rules (in the form of '-:') will generally only speed up server-side checkouts, unless you use Perforce and TFS agent-side checkout, where exclude rules are processed in an effective manner. So, to cut a long story short, I noticed that the path to the specific file was slightly different from the other working ones. : No labeling rules found for checkout rules branches/1.1=>branches/1.1Īt .(SvnSupport.java:36)Īt .tLabel(VcsLabeler.java:40)Īt .tLabel(VcsLabeler.java:52)Īt .tLabel(FinishedBuildImpl.java:16) The build checkout directory is a directory on the TeamCity agent machine where all the sources of all builds are checked out into. So firstly, I tried removing all the checkout rules to confirm it was picking up file changes - this worked. When I try to tag the build from the changes "Label this build source" I get the following:įailed: Failed to set label 'test': No labeling rules found for checkout rules branches/1.1=>branches/1.1 When creating the checkout rules, you have the option to leave the folder structure the same as it is in your VCS or you can remap the struture to suit your needs. In the above example, the first rule excludes the src/help directory and its contents from checkout. For each root, you can specify what folders are of interest to you with the Checkout Rules. This will prevent the triggering of a new build. Assuming that the buildserver commits the new version number and is using a unique Git account, the checkout rule can be adjusted to ignore the commit of the teamcity git user. ![]() My VCS root is defines as the following in TC: An example with three VCS checkout rules: -:src/help. If no trigger rules are specified, a build is triggered upon any change detected for the build configuration. Another option is to use the checkout rules to ignore the commit from the buildserver.
0 Comments
Leave a Reply. |