Hello! On Thu, Jun 9, 2016 at 11:45 AM, Carl Reid <[email protected]> wrote:
> I have tried to stop this from happening by changing the "autoUpdate" > attribute of the <TFS> element in the materials section of the config xml > to "false" then checking-in the changes. However all this seems to do is > temporarily disable the notification. > As soon as the autoUpdate is set back to "true" all the pipelines trigger > again and cause the problem described above. > > Is there any way of temporary suspending auto update such that changes to > script materials do not cause pipelines to execute? > It looks like you need a "Blacklist <https://docs.go.cd/current/configuration/admin_add_material.html#blacklist>" filter added to your material. I've used it before to ignore changes to files like a README, etc. Don't turn autoUpdate off, though. Once you set the blacklist, it should stop triggering a pipeline upon change of files in the blacklist. However, once the pipeline triggers (due to something else), you want the autoUpdate to have happened, so that it picks the latest of those scripts in the scripts repo. Hope that works, 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.
