The CPaaS build-pipeline skips builds when there have been no changes to dist-git. 

However, due to some misconfigurations in our CPaaS build pipeline, it is common for this to happen: 

Successful 2 build(s):
  name: apicast-operator-bundle-brew-container, nvr: 3scale-apicast-operator-bundle-container-2.12.0-645, taskInfo: 49697413
  name: 3scale-operator-bundle-brew-container, nvr: 3scale-operator-bundle-container-2.13.0-284, taskInfo: 49697412

Skipped 9 build(s):
  name: system-brew-container
  name: memcached-brew-container
  name: 3scale-operator-brew-container
  name: backend-brew-container
  name: zync-brew-container
  name: auth-wasm-brew-container
  name: apicast-operator-brew-container
  name: toolbox-brew-container
  name: apicast-brew-container

The reason this happens is because our CPaaS midstream configuration does create changes in dist-git, e.g. like so: 

https://pkgs.devel.redhat.com/cgit/containers/3scale-operator-prod-operator-metadata/log/?h=3scale-amp-2 

2 mechanisms change dist-git content and currently seem a little misaligned: 

• CPaaS Midstream dist-git maker, through the `.in` template files 
• CPaaS Midstream render-templates mechanism 

I am creating this ticket to investigate why this happens and get rid of all cases when this happens: 

• for both 3scale-operator and apicast-operator bundle images
• across all alpha, Managed Application Services (MAS) and stable release streams.