All of our project-specific CSITs builds have been failing since 4/29. They don't even get to the first step of invoking the "run" script. An example can be found in:

https://jenkins.onap.org/view/policy/job/policy-api-master-project-csit-api/105/

Excerpt from the console output:
07:22:46 [EnvInject] - Injecting environment variables from a build step.
07:22:46 [EnvInject] - Injecting as environment variables the properties file path 'env.properties'
07:22:46 [EnvInject] - Variables injected successfully.
07:22:46 [policy-api-master-project-csit-api] $ /bin/sh -xe /tmp/jenkins483093341050399641.sh
07:22:46 + /w/workspace/policy-api-master-project-csit-api/csit/run-project-csit.sh api
07:22:46 /tmp/jenkins483093341050399641.sh: 2: /tmp/jenkins483093341050399641.sh: /w/workspace/policy-api-master-project-csit-api/csit/run-project-csit.sh: not found
07:22:46 Build step 'Execute shell' marked build as failure

Feedback from Jess:

I do noticed that this template is designed to use the "gerrit" strategy to build instead of "default" which can cause builds to happen in not the latest master tip:

https://github.com/onap/ci-management/blob/master/jjb/policy/policy-csit-jobs.yaml#L28