I have an automated server which installs and runs tests against all Meteor versions once they are released. I created it to make sure Minimeteor doesn’t break with newly released versions.
I get the list of available Meteor versions from the GitHub releases page: https://github.com/meteor/meteor/releases
Usually, a new release isn’t ready for download for a day or two. But for Meteor 1.4.4.5, it’s showing an error since a week now:
$ curl https://install.meteor.com/?release=1.4.4.5 | sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 7786 0 7786 0 0 18758 0 --:--:-- --:--:-- --:--:-- 18806
Downloading Meteor distribution
Retrying download in 5 seconds...
Retrying download in 5 seconds...
Retrying download in 5 seconds...
Retrying download in 5 seconds...
Retrying download in 5 seconds...
And then it fails.
My question is about the Meteor release process: what’s happening between creating a GitHub release and making it available for download, and how could I maybe improve my test process?