https://jira.akraino.org This file is an XML representation of an issue en-us 9.4.5 940005 11-04-2023 https://jira.akraino.org/browse/VAL-95 Validation <p>image_tag=$( (git branch || echo "* local") | grep "^&#42;" | awk '</p> {print $2} <p>')</p> <p>The blucon.sh script should also be called from ci-management git in ci. <br/> Before setting the image tag, the script should change directory to validation and after finding the image tag should go to parent folder.</p> VAL-95

blucon.sh script assumes that it is run in validation git

Bug Medium Done Done Alexandru Avadanii Valentin Radulescu Tue, 31 Dec 2019 09:47:46 +0000 Wed, 22 Apr 2020 12:15:18 +0000 Wed, 22 Apr 2020 12:15:18 +0000 0 3 <p>The bug description is not very clear, hence the confusion.</p> <p>The problem is not that blucon.sh runs in the context of a git repository, but that it makes 2 assumptions which are not true in the context of the CI runs:</p> <ul> <li>the validation git repository is located in the "validation" directory (hardcoded dir name), while in CI it might be cloned in the current job workspace, called for example "bluval-daily-master";</li> <li>the "results" dir will be created in the "validation" directory parent, while in CI we expect the "results" directory to be inside the "validation" git repository;</li> </ul> <p>The pathches I proposed maintain the current behavior by default, but also allow customizing the 2 paths (for "validation" and "results" directories) via env vars that we will set for the CI runs.</p> <p>in your case it will create a images "akraino/validation:blucon-local" and that should work without any issues.<br/> If we do as you said that will create an image "akraino/validation:blucon-master". Expect the images tag there will not be any difference.</p> <p>I can do a fix if you still need an enhancement.</p> Development Rank 0|i00304: