Hi Aravind, thanks for answer, case that i want that any commit to private git repo always triggers pipeline and it does, but github repo is pulled too, which is fine , but whitelist doesnot work , because build is done based on the latest commit on github (few days ago). And few days ago, this commit did not trigger the pipeline , making me thinking that somehow upon the commit to another material, the whitelist is ignored for another material and it pulled anyway to the latest revesion.
On Thursday, 5 April 2018 14:07:20 UTC+2, Aravind SV wrote: > > If you don't want the private git repo to be considered, then shouldn't > you blacklist it completely? (as in **/*) > > On Thu, Apr 5, 2018 at 5:21 AM, Oleg Mayko <[email protected] > <javascript:>> wrote: > >> Hi All, >> there is the build pipeline which have 2 materials one is github repo >> with source code and one is private git repo with config files and scripts. >> So, i configured whitelist that github repo should be polled upon commit >> in VERSION file , which means releasing of new version. However, if i do a >> commit to private git repo, the github repo get pulled anyhow with last >> commits and then build is triggered upon them; what is of course not how i >> imagine this to work. >> what could be the solution to it? do i misundersand the go-concepts ? >> >> Thank you >> Regards >> Oleg >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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.
