MeFisto94
commented
4 years ago We could use the github actions run id at least for the last version part (we just need to check how to do this with ant). This doesn't help that every module is bumped. Technically to tackle that, we should only rebuild modules when they are changed (i.e. when every module was their own git repo) and then they just update the XML partially. But that doesn't hold good with our current infrastructure, which is deleting releases every 3rd commit.
We need to come up with a versioning scheme, specifically for nightlies, where we can't manually bump the version. The problem is that the current version always is 3.3.0.1 and the installed SDK always has 3.3.0.0, causing nightlies update to only be available once I guess and also downloading all modules, even if they remain unchanged.
Maybe some git extract magic? We could get the commit difference since the last tag or something, but using that to hand out different versions for every module might not work/break.