fix: gradle tasks from different subproject are not isolated

[ata-nas]

What Happened

Due to some concerns that arose in #264, there are repeating task names createDockerImage (outside the scope of the issue, but inside the scope of the discussion #264) which do touch on a common file that gets created via a shell script update-env and in the asynchronous nature of the running of the tasks, it could happen that a project gets build with the wrong values that come from the common .env file.

What should happen

All tasks (especially those that have the same task names) must run in an isolated fashion, not going outside the subproject build root.
Subprojects may share common scripts and files, but must not write files outside the current subproject build root. Copying inputs or scripts between subprojects is acceptable if this improves task isolation.

[AlfredoG87]

@ata-nas can we close this one too?

[ata-nas]

@ata-nas can we close this one too?

@AlfredoG87 we cannot close this one, it is the result of the #264 discussion. We have non-deterministic behavior, since we have files that are being produced by the tasks which go outside the respective build root. This must be fixed and to be ensured that it will no longer be the case.

That being said, maybe #332 may be a duplicate of this one and could be closed?

[AlfredoG87]

@ata-nas can we close this one too?

@AlfredoG87 we cannot close this one, it is the result of the #264 discussion. We have non-deterministic behavior, since we have files that are being produced by the tasks which go outside the respective build root. This must be fixed and to be ensured that it will no longer be the case.

That being said, maybe #332 may be a duplicate of this one and could be closed?

Is not a duplicate, I don't think the gradle tasks being isolated is the same as docker image being built deterministically.
lets keep both open for now.