Travis configuration issue? about streamlink-portable

[beardypig]

It is by design :-)

They are built once a day (plus once for any script change), this is because it's triggered by a cronjob in travis, and there isn't a super clean way to only build if streamlink has changed. You'd have to store the last commit and only build if it changes, I don't think travis has the ability store variables like that... I could remove the date from the zip file name so that it overwrites any existing one with the same commit, but then you lose the nice ordering in the file names. I have set up S3 to remove builds older than 60 days, so the space it takes on S3 is limited to around 2GB which costs me around $1 per year :-)

It might be possible to setup a webhook from the streamlink repo to build this one on a change.

Also, I plan to add "stable" versions that are built from tags on the streamlink repo :-)

[beardypig]

Although, thinking about it now, maybe I can use the date of the last commit for the date... That would be much better. It would still build everyday, but wouldn't keep added zips when nothing changes :-)

Thanks for the idea :-D

[beardypig]

Hmm, thinking even more about it, the commit date might not be 100% reliable as there is no guarantee of chronological order in git :-(

[beardypig]

I have updated it to use the last commit date, it should be fine as streamlink always merges from pull requests.