Hello, Sorry, didn't realize you'd asked a question.
On Sun, Jul 17, 2016 at 2:58 AM, <[email protected]> wrote: > 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. > You said: "Materials are polled/downloaded on the GoCD server". That is correct. You said: "and transferred to an agent when required". This is *not correct*. Agents also use svn/git, etc. to update the repository they have (or will clone a repository) to the *correct revision *for that pipeline run. The correct revision is not always the latest. You said: "The server fetches new material only on a manual trigger of a pipeline or via polling". That is correct too, with an addition that the notify material API <https://api.go.cd/current/#notify-git-materials> can also cause it to happen, if polling is turned off. 2. The stage setting 'Fetch Materials' refers to fetching from the gocd > server (and not the actual SCM)? > Based on what I said earlier, it is not about fetching from the GoCD server, but it is about the actual SCM. However, the setting refers to the agent-side checkout/clone/update. So, you're partially right. 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.* > It will retrieve the latest version that the GoCD server is aware of, but not *from* the GoCD server as mentioned earlier. It'll just be updating its local checkout of the repository to the latest version that the server is aware of, directly from the SCM repository. 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. > Yes, that is right. The way it is now. Truly, the material concept is a global concept and not a pipeline-level concept and that is how it should have been modeled. 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.
