plz support?
(as i understand it...) some custom trickery is currently done to get it to work at all...
SPADS doesnt recognise maintenance builds
Moderators: Moderators, Lobby Developers, SPADS AutoHost
Re: SPADS AutoHost
Can't seem to be able to use maintenance builds from the maintenance branch ( https://springrts.com/dl/buildbot/default/maintenance/ )
'testing' for autoManagedSpringVersion also just picks stable 104.0.
NOTICE - [SPADS] Initializing SPADS 0.12.2a
ERROR - [SpadsUpdater] Spring 104.0.1-151-g11de57d installation cancelled (version unavailable for download)
CRITICAL - [SPADS] Unable to auto-install Spring version "104.0.1-151-g11de57d"
As a temporary workaround, I manually created the ~/.spads/var/spring/104.0.1-151-g11de57d-linux64 directory and put the particular Spring version there.
'testing' for autoManagedSpringVersion also just picks stable 104.0.
NOTICE - [SPADS] Initializing SPADS 0.12.2a
ERROR - [SpadsUpdater] Spring 104.0.1-151-g11de57d installation cancelled (version unavailable for download)
CRITICAL - [SPADS] Unable to auto-install Spring version "104.0.1-151-g11de57d"
As a temporary workaround, I manually created the ~/.spads/var/spring/104.0.1-151-g11de57d-linux64 directory and put the particular Spring version there.
Re: SPADS AutoHost
I finally found some time to add maintenance branch support into Spring version auto-management functionality: the autoManagedSpringVersion setting now accepts the "maintenance" value to automatically stay up to date with Spring maintenance branch (only available in SPADS >= 0.12.4).
This is the expected behavior, given than current Spring "testing" version (103.0.1-1328-g882485f as seen here) is older than latest available release (104.0).tzaeru wrote:'testing' for autoManagedSpringVersion also just picks stable 104.0.
Yes, this should work nicely.tzaeru wrote:NOTICE - [SPADS] Initializing SPADS 0.12.2a
ERROR - [SpadsUpdater] Spring 104.0.1-151-g11de57d installation cancelled (version unavailable for download)
CRITICAL - [SPADS] Unable to auto-install Spring version "104.0.1-151-g11de57d"
As a temporary workaround, I manually created the ~/.spads/var/spring/104.0.1-151-g11de57d-linux64 directory and put the particular Spring version there.