release-monitoring: Don't use cached layers

The cached layers were root issue of having outdated anitya date,
because the step wasn't run again if there was no change in the
Dockerfile for the step, the cached version was used instead.

Signed-off-by: Michal Konečný <mkonecny@redhat.com>

roles/openshift-apps/release-monitoring/files/deploymentconfig.yml

@@ -19,7 +19,7 @@ items:
           failurePolicy: Abort
           execNewPod:
             containerName: release-monitoring-web
-            command: [ /bin/sh, -i, -c, "ls -l /usr/local/lib/python3.8/site-packages/anitya/db/migrations/versions/;alembic-3 -c /etc/anitya/alembic.ini history; alembic-3 -c /etc/anitya/alembic.ini upgrade head" ]
+            command: [ /bin/sh, -i, -c, "alembic-3 -c /etc/anitya/alembic.ini upgrade head" ]
             volumes:
               - config-volume
       resources: {}

roles/openshift-apps/release-monitoring/templates/buildconfig.yml

@@ -44,7 +44,7 @@ items:
                 python3-wtforms && \
             dnf autoremove -y && \
             dnf clean all -y
-        RUN echo $(git clone https://github.com/fedora-infra/anitya.git && \
+        RUN git clone https://github.com/fedora-infra/anitya.git && \
                 pushd anitya && \
 {% if env == 'staging' %}
                 git checkout staging && \
@@ -65,7 +65,7 @@ items:
                 pip-3 install . && \
                 popd && \
                 popd && \
-                rm -rf anitya)
+                rm -rf anitya
         # Let's use staging auth server in staging
 {% if env == 'staging' %}
         RUN sed -i 's/id.fedoraproject.org/id.stg.fedoraproject.org/g' /usr/lib/python3.8/site-packages/social_core/backends/fedora.py
@@ -84,6 +84,8 @@ items:
 {% endif %}
     strategy:
       type: Docker
+      dockerStrategy:
+        noCache: true
     output:
       to:
         kind: ImageStreamTag