Right now github interactions api downloads the artifact to the bucket. But the problem is that VM uses the artifact on the bucket. But what will happen if another VM will be created and github-interactions-api will download artifact? It will override the existing one.
Therefore my suggestion is, to change the path in which the artifact is downloaded according to the identificatior of the test-run. For example, artifact will be downloaded to the following path /bucket/ea28s1804712e/ccextractor. Also, it is important to specify path to the ccextractor associated with the identificator of the test-run.
Also, github-interactions-api service should be called from the orchesetration library for each test run.
Right now
github interactions apidownloads the artifact to the bucket. But the problem is that VM uses the artifact on the bucket. But what will happen if another VM will be created andgithub-interactions-apiwill download artifact? It will override the existing one.Therefore my suggestion is, to change the path in which the artifact is downloaded according to the identificatior of the test-run. For example, artifact will be downloaded to the following path
/bucket/ea28s1804712e/ccextractor. Also, it is important to specify path to the ccextractor associated with the identificator of the test-run.Also,
github-interactions-apiservice should be called from the orchesetration library for each test run.