Thank you very much for the information. I have found a detailed guide to configure Travis CI:
But my projects are in subversion repositories and it seems Travis CI only works with Git, so i tested the packager with a minor project and it's working well locally. It's specially useful the posibility to ignore files, because usually the classic version requires additional libraries and code, so this libraries and extra files can be removed from the retail zip file.
Some extra useful info and possible issues:
- At least with subversion repositories, the packager does not work well in a non-english language (fails getting svn information), so the OS language must be changed to english before running "release.sh", executing in bash the commands:
- The packager works in Windows through Cygwin (https://www.cygwin.com/), but some additional cygwin packages must be installed:
curl zip jq git subversion
- Maybe this was obvious to everyone else but I just realized that now CurseForge and WowAce repositories are fully merged, they are the same, so ZIP files can be uploaded to CurseForge to update WowAce projects. But It seems this was not possible time ago (One year ago CurseForge api key could no be used to upload to WoWace and the WowAce upload api was disabled). So now simply assign the WowAce API TOKEN to the"CF_API_KEY" enviroment variable and the packager will upload the ZIP files to WowAce.