Thanks Chad I've done some more investigation and you're right - there's some upstream pipelines set to "Regularly fetch updates to this repository" rather than our company strategy of "Fetch updates only on webhook or manual trigger". I wasn't aware that upstream material configurations could affect downstream ones. We rely on templates for the majority of our pipeline creations, and use an in-house tool (relying on GoCD APIs) that explicitly specify 'autoUpdate="false"'. It's been a while since I've created a pipeline from the GoCD wizard or from scratch, so not sure if this has always been the case, but through the GoCD GUI Create Pipeline workflow, the material configuration is selected *before* a template is chosen, meaning templates cannot control advanced material configuration, such as autoUpdate="false". Unless the user selects this from the material Advanced menu at the time, the default is essentially 'autoUpdate="true"'. I think that a bunch of these has crept in since I last cleared them up.
For posterity for anyone else reading this, some contextual info is useful to know: 1. When "Regularly fetch updates to this repository" is selected, it is not explicitly expressed in the XML. Its absence on the line beginning <git url=" under the material configuration defines it, somewhat unintuitively. For instance, if you set autoUpdate="true", GoCD will simply delete the key value pair, and "Regularly fetch updates to this repository" is selected. 2. When "Fetch updates to this repository only on webhook or manual trigger" is selected, on the line beginning <git url=" the property of autoUpdate="false" appears to show this in the XML. 3. This property must be the same over all pipelines which use the same material. You cannot have one pipeline which pulls and one which receives a push for the same material. On Friday, November 17, 2023 at 2:54:32 AM UTC Chad Wilson wrote: > In theory if you have disabled polling on all usages of the material (via > its URL/branch combination), and there are no triggers from webhooks, APIs > or elsewhere then it shouldn't be trying to do modification checks that > generate such an error. > > [image: image.png] > Having said that, I wouldn't *entirely* be surprised if there is some > other kind of trigger for an update/modification check, e.g as a side > effect of an upstream pipeline completing (if there is one) or a server > restart, even if that is not intended. > > If you have disabled that polling everywhere and are still seeing the > error appear, it'd be interesting to know if you can figure out when it is > triggered. > > -Chad > > > On Fri, Nov 17, 2023 at 5:51 AM 'Chris Gillatt' via go-cd < > [email protected]> wrote: > >> Hi all >> >> Is there a way to exclude a pipeline or pipeline group from the material >> checks? >> >> [image: Screenshot 2023-11-16 at 16.43.17.png] >> We have a use-case in my business where a release pipeline's material is >> pointed at a specific, temporary branch in GitHub. The branch is pushed >> to, and the pipeline triggers via a push from a GitHub webhook (opposed to >> a pull from the GoCD poller). The webhook in GitHub is configured to only >> notify on push changes. Once the branch triggers the pipeline and it >> succeeds, the branch is deleted in GitHub. Until a new temporary branch is >> pushed to the repository, the existing one set in GoCD becomes invalid. >> GoCD somehow notices this, and reports this material problem in the >> warning/error button found on the top right of the GUI. For us, the >> problem is that warnings/errors we care about are sometimes lost in this >> list of ones we don't. It'd be nice if we could exclude some pipelines >> from this check. There doesn't appear to be an obvious way to do this, and >> I suspect that it's just not a supported feature. >> >> Cheers >> Chris >> >> -- >> 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]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/go-cd/b0a6f0aa-44c6-4e76-b65b-715b7c45ad55n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/go-cd/b0a6f0aa-44c6-4e76-b65b-715b7c45ad55n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/19d266e2-05b3-4c1c-a624-920da5eb6026n%40googlegroups.com.
