CI not Pushing Builds to S3

[techman83]

The latest build on S3 is from October 20. Noted in #2189 as Netkan Bot hadn't picked up the fixed Curse API.

leon@beast /tmp $ (rm netkan.exe || true) && wget -q http://ckan-travis.s3-website-us-east-1.amazonaws.com/netkan.exe && mono netkan.exe --version
rm: cannot remove 'netkan.exe': No such file or directory
v1.22.7-PRE+bd1c5daa6a5a

[HebaruSan]

Browsing the commit history, .travis.yml was changed the day after that, in 2ab5dce and 9433258 , but it's not clear to me why that would have caused any problems.

@dbent, do you see anything fishy there?

EDIT: This is the latest job with config=Release and mono=5.4.0:

https://travis-ci.org/KSP-CKAN/CKAN/jobs/305483643#L2534

Skipping a deployment with the s3 provider because a custom condition was not met

The custom condition checks that the mono version matches 5.4.0 using a perl regex:

        condition: $BUILD_CONFIGURATION = Release && $(mono --version | perl -ne'/version (\S+)/ and print $1') = $BUILD_RELEASE_MONO_VERSION

But instead of 5.4.0, mono --version prints 5.4.0.201:

$ mono --version
Mono JIT compiler version 5.4.0.201 (tarball Fri Oct 13 21:47:28 UTC 2017)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
	TLS:           __thread
	SIGSEGV:       altstack
	Notifications: epoll
	Architecture:  amd64
	Disabled:      none
	Misc:          softdebug 
	LLVM:          supported, not enabled.
	GC:            sgen (concurrent by default)

Presumably we cannot hard code the .201 suffix because it might change. So should we strip it out?

[techman83]

And we're good. The netkan bot will pick up the new version on the next run.

➜  /tmp (rm netkan.exe || true) && wget -q http://ckan-travis.s3-website-us-east-1.amazonaws.com/netkan.exe && mono netkan.exe --version
rm: cannot remove 'netkan.exe': No such file or directory
v1.24.0-PRE+0eacb1575574