The test script run in the CI environment is defined in Jenkins. Hence, all the PRs are tested under the very same circunstances.
That's not a good practice, since a chage that requires updating that script would interfere in the tests of every other PR. Either that PR or any other PR would be broken.
Adding this script into azk source code would keep things apart and would solve this issue.
Plus, Jenkins have to be updated as well, in order to call this new script from azk source code.
The test script run in the CI environment is defined in Jenkins. Hence, all the PRs are tested under the very same circunstances.
That's not a good practice, since a chage that requires updating that script would interfere in the tests of every other PR. Either that PR or any other PR would be broken.
Adding this script into azk source code would keep things apart and would solve this issue. Plus, Jenkins have to be updated as well, in order to call this new script from azk source code.