anchor.diff:  Git - g3 : poll for new changes disabled with no blacklisting.
   Git - g4 : poll for new changes enabled with no blacklisting.
   
  -    <img src="/assets/images/blog/cd-hacks/material-blacklisting.jpeg" alt="Blacklisting Materials in GoCD"/>
  +<img src="/assets/images/blog/cd-hacks/material-blacklisting.jpeg" alt="Blacklisting Materials in GoCD"/>
       
   Here’s a breakdown of how your pipeline behaves when there are commits made to the source code materials. 
   
  
positive.code: 
  The "Fetch Materials" option, on the other hand, affects only the Agent side. It's an option which allows the agent to not fetch / checkout / clone the materials at all, when run. By this time, the server has already decided which materials to use. The agent cannot control it.
  
  INSERT IMAGE HERE
  
  When Fetch Material is set to False.
  `<stage name="stagename" fetchMaterials="false">`
  
  “Fetch materials” option should be turned off only in cases where you don't care about the material at all. In some cases, you just want a timer trigger for a pipeline - and don't care about the revision of the checked out material - or you want to check out the material yourself for some reason. Then, you'd turn off "Fetch materials".
  
negative.code: 
  In order to perform whitelisting, you choose “Invert the file filter, e.g. a blacklist becomes a whitelist instead.” option as shown below.
  
  <img src="/assets/images/blog/cd-hacks/edit_material_whitelist.png" alt="GoCD Fetch Materials"/>
  
  ##Server-side Material Blacklisting vs Fetch Materials
  
  