Hello! On Tue, Jul 5, 2016 at 7:59 AM, <[email protected]> wrote:
> Is the only way to get the material to update is to set polling to true > and blacklist **/* ? > How should I update my configuration? > I already have many pipelines which use this repository and more which use > different branches in the same repository. Am I supposed to manually change > the configuration file for all of these pipelines? For all branches? > > > Is this by design? I really want to understand why this is happening. > Shouldn't a new build of the pipeline (2) use an updated version of the > material? > You mentioned that you've turned off polling. So, those materials are not polling (and hence, are not updated). Why (and how) would you expect a pipeline in GoCD to know that a material has a new commit (and needs to trigger) if polling is turned off? Maybe you're thinking of using the notification API <https://api.go.cd/current/#notify-git-materials> to push instead of poll? Would help to know more about what you're trying to do. Usually, you set polling to true and use the blacklist (as you mention) in case you want the pipelines to pick the latest materials, but not trigger upon commits to the materials. Cheers, Aravind -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
