gchiu
1
Just wondering how feasible it is for Travis to also upload the latest build in a latest folder so that the URL remains fixed
So, instead of going, for example, to
http://metaeducation.s3.amazonaws.com/travis-builds/0.3.40/r3-4f44c19-debug-cpp.exe
for the current latest build, we can go to
http://metaeducation.s3.amazonaws.com/travis-builds/latest/0.3.40/r3.exe
This would make things easier to publish documents in case people need to use wget
etc.
2 Likes
I like this. But I'm also wondering about version releases? - Criteria for stable r3/ren-c releases
So is it possible to also keep last version release on Travis? Something like this...
http://metaeducation.s3.amazonaws.com/travis-builds/version/2.102.0.3.40/r3.exe
Or would we need to copy off and serve from elsewhere?
gchiu
3
If we can't script it, then yes, that may be what we have to do.
Any takers for the task?
I'm happy to include this as part of updating CHANGES when there is a version release.