Edit: replaced by this updated launcher thread - moved this one to Suggestions as a dupe
Name: Launcher, automated updates, and versioning
Summary: Automate the versioning and updating of the main app via build script on the server side and a launcher on the client side
Scope: Engine
Current Goal: Initial launcher downloading the latest version (and where to keep a version tag)
Phase: Implementation
Curator: NowNewStart plus maybe Kai Kratz and x3ro along with mkalb from GitHub
Related: #62, #67, #167, #171, #221, #287
New contributor NowNewStart offered to make us a launcher to pull automated updates for Terasology off the web (thanks!). This relates to multiple existing issues I've linked above. Trick is: We don't have fully integrated versioning yet
I've played with version numbering in the past (we'd technically be at 0.43 or so at this point) but it hasn't been automated or put to use for anything. There are/were even hooks for it in the Gradle build script.
http://jenkins.movingblocks.net/job/Terasology/lastSuccessfulBuild/? might be a good in-between to tell the launcher to check for updated builds (can parse the build number off the page). Still need something in the client for it to know what build it is, however, which I think we'd need in the Gradle script
Name: Launcher, automated updates, and versioning
Summary: Automate the versioning and updating of the main app via build script on the server side and a launcher on the client side
Scope: Engine
Current Goal: Initial launcher downloading the latest version (and where to keep a version tag)
Phase: Implementation
Curator: NowNewStart plus maybe Kai Kratz and x3ro along with mkalb from GitHub
Related: #62, #67, #167, #171, #221, #287
New contributor NowNewStart offered to make us a launcher to pull automated updates for Terasology off the web (thanks!). This relates to multiple existing issues I've linked above. Trick is: We don't have fully integrated versioning yet
I've played with version numbering in the past (we'd technically be at 0.43 or so at this point) but it hasn't been automated or put to use for anything. There are/were even hooks for it in the Gradle build script.
http://jenkins.movingblocks.net/job/Terasology/lastSuccessfulBuild/? might be a good in-between to tell the launcher to check for updated builds (can parse the build number off the page). Still need something in the client for it to know what build it is, however, which I think we'd need in the Gradle script
Last edited: