> Did this. Next builds _should_ be back to their old urls. Great! Thanks Leo. :)
On 25 September 2014 00:04, Leo Simons <lsim...@schubergphilis.com> wrote: > On Sep 24, 2014, at 5:33 PM, Ian Duffy <i...@ianduffy.ie> wrote: > >> Aren’t they published to S3 somewhere? It’d probably be better if users > > fetch systemvms from S3…… > > > > Both not a clue what the S3 urls are though. > > Based on > > http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201402.mbox/%3c3f6b7b36-32a2-4f11-aeff-36a400d67...@gmail.com%3E > > It ought to be > > https://s3.amazonaws.com/systemvm-templates.cloudstack.org/master/32/systemvmtemplate-master-xen.vhd.bz2 > > https://s3.amazonaws.com/systemvm-templates.cloudstack.org/master/64/systemvm64template-master-xen.vhd.bz2 > > and so forth but I’m getting permission denied. Hugo, any idea? > > >>> Isn't this what we use /etc/cloudstack-release for? > >>> You could include extra information in there if you wish, version, > >> branch, > >>> git sha1, etc. which would give great traceability. > >> > >> Sounds like a plan. I’ll see about submitting a patch tonight. The issue > >> is that /etc/cloudstack-release is parsed in a location or two (I forget > >> the details) so it kind-of has to match existing regexes. > > Grmbl is all I have to say. > > >> In the meantime... > >> export BUILD_NUMBER= > >> at the right place in the relevant build job should fix the immediate > >> issue... > > Did this. Next builds _should_ be back to their old urls. > > > g’night! > > > Leo > >
