Thanks Aravind for the detailed explanation. It really helped us understand the process better.
I'd like to post one last clarification and ask if this is correct: 1. Materials are polled/downloaded on the gocd Server (and transferred to an agent when required). The server fetches new material only on a manual trigger of a pipeline or via polling. 2. The stage setting 'Fetch Materials' refers to fetching from the gocd server (and not the actual SCM)? So, If polling is not enabled, and the pipeline is triggered i.e by an upstream pipeline - the agent will retrieve the latest version on the *gocd server.* Am I correct in this? Also, If you have any tips on reconfiguring many pipelines to use polling with blacklists (we have about 30 which do not currently use polling) i'd reall appreciate it. Finally - Just for everyone to know - it seems that gocd recognises a material repository according to its unique URL. So, for git repos at least, [email protected]:myrepo/repo1 and [email protected]:myrepo/repo1.git will be treated as separate material repos. each can have separate polling settings although they will both be pulling from the same github repo. This might cause problems in troubleshooting issues, if some users define the repo differently. But on the other hand, it may help to change the polling setting when several pipelines are already configured with the same material. Otherwise, one would have to change the setting for all of the pipelines via the config XML. Thanks again for the assistance, On Tuesday, July 5, 2016 at 2:59:03 PM UTC+3, [email protected] wrote: > > Hi everyone, > > I'm using gocd version 16.3.0. > Pipeline 1 with git material A, Downstream pipeline 2 with git material B > with automatic scheduling. > All git materials set not to poll, all stages set to fetch materials. > > When pipeline 2 is triggered (automatically) by success of pipeline 1 - *git > materials in pipeline 2 are NOT updated*. > > I have seen this behaviour referenced in > https://github.com/gocd/gocd/issues/948 and > https://github.com/gocd/documentation/issues/98 > > > 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? > > Finally - I'd like to suggest a feature that will enable setting of > polling for all relevant stages/pipelines. This can either be done through > a new 'materials' page which will list the materials and associated > stages/pipelines OR by adding this as an option in the warning dialog which > appears when a user tries to change polling (and more than one stage is > referencing that material) > -- 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.
