> Did this. Next builds _should_ be back to their old urls.
Great! Thanks Leo. :)
On 25 September 2014 00:04, Leo Simons wrote:
> On Sep 24, 2014, at 5:33 PM, Ian Duffy wrote:
> >> Aren’t they published to S3 somewhere? It’d probably be better if users
> > fetch systemvms from S3……
> >
> > Bot
On Sep 24, 2014, at 5:33 PM, Ian Duffy 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
> 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.
> though one wonders why users need to fetch
systemvms built from master at all…
Ease of access for running from the latest master branch I'd imagine.
On Sep 24, 2014, at 11:26 AM, Ian Duffy wrote:
>> The general concept is one of traceable and repeatable builds.
>
> In the context of jenkins.buildacloud.org I would disagree with this. Only
> two build jobs are ever kept. When a time arises when you need to figure
> out what commit your systemv
> The general concept is one of traceable and repeatable builds.
In the context of jenkins.buildacloud.org I would disagree with this. Only
two build jobs are ever kept. When a time arises when you need to figure
out what commit your systemvm was based of I'd be willing to bet that job
has been cl
Hey Ian,
On Sep 24, 2014, at 2:04 AM, Ian Duffy wrote:
> I noticed the filename of the generated systemvms changed on
> http://jenkins.buildacloud.org/job/build-systemvm64-master/
>
> They now include a [0-9]* before the hypervisor name representing the build
> number.
That’s one of the things
Hi All,
I noticed the filename of the generated systemvms changed on
http://jenkins.buildacloud.org/job/build-systemvm64-master/
They now include a [0-9]* before the hypervisor name representing the build
number.
Why do we do this? Its annoying for external resources linking to the last
successf
