Changed perforce stream paths not triggering new builds

Avatar
Sam
Created

We recently added an import to our perforce stream paths so that it looks like this:

share ...
import Projects/Game/Plugins/PluginOne/... //depot_root/plugins_stream/PluginOne/...
import Projects/Game/Plugins/PluginTwo/... //depot_root/plugins_stream/PluginTwo/...  <-- This is the new line

The issue we are having is that changes to files in //depot_root/plugins_stream/PluginTwo/... aren't triggering builds in our stream. This is working fine for changes in the PluginOne folder, so not sure what is causing this. It feels like TeamCity is caching a stream view somewhere that hasn't been updated?

 

Any help would be appreciated,

 

Thanks.

 

Votes

0

Share

2 comments
Avatar
Guilherme Barbosa
Created

Hi Sam,

Did you also reflect the new changes in your VCS Root configuration? Perhaps you can share details on the VCS root and Perforce Shelve Trigger configuration so that we can try to reproduce the issue.

Thanks

0
Avatar
Sam
Created

Hi Guilherme,

Thanks for the reply.

I didn't make any changes to our VCS Root configuration. It is just a default perforce root with the stream set to one we modified.

Weirdly it has now started working, so I guess whatever was being cached got updated.

0

Please sign in to leave a comment.