1271053 - Flame transition build

Status: RESOLVED FIXED

(Firefox OS Graveyard :: B2gInstaller, defect)

Description

[Jovan Gerodetti]

I would like to add my flame transition build. 
I'm going to try to update it weekly.

Comment 1

[Jovan Gerodetti]

Attachment: TitanNano:master > mozilla-b2g:master

Comment 2

[:gerard-majax]

Thanks for your PR!

Are you sure this is working? I cannot your URL to work with curl. You should make sure this works by:
 - open about:config
 - right click, add new value
 - make it a string value, being named [e-mail]
 - use the builds.json of your PR as value: https://raw.githubusercontent.com/TitanNano/b2g-installer-builds/master/builds.json
 - unplug your flame
 - reload the about:b2g-installer tab
 - replug your flame

You should be able to install it.

From your link, it looks like the real good URL working with curl is: https://googledrive.com/host/0B179vm24EW9AV1l3WklqN25lMEE/flame/flame.blobfree-dist.latest.zip

Comment 3

[Jovan Gerodetti]

You are right. 

I fixed the url and the add-on was able to download the build for me.

Comment 4

[:gerard-majax]

Comment on attachment 8750003 [details] [review]
TitanNano:master > mozilla-b2g:master

Thanks! I will just need that you squash all your commits into one, and change the commit title to "Bug 1271053 - Flame transition build added r=gerard-majax". Then flag me needinfo? and I'll merge this!

Comment 5

[Jovan Gerodetti]

no problem, done.

Comment 6

[:gerard-majax]

https://github.com/mozilla-b2g/b2g-installer-builds/commit/b0584a4448abcddf9b3519a23675b27934dc3a02

Comment 7

[:gerard-majax]

thanks!

Comment 8

[:gerard-majax]

I have a problem, I'm not able to download your build from the addon. Downloading via curl works though. Can you check on your side?

Comment 9

[:gerard-majax]

Ok, it worked, but there is no progress information when using your hosting :/

Comment 10

[Jovan Gerodetti]

Hmmm I see. 
This is probably googles fault and not something we can fix?

Comment 11

[:gerard-majax]

I cannot tell, maybe we should be smarter in the way we display it :)

Comment 12

[Jovan Gerodetti]

Google doesn't send a Content-Length so we can't know how much we will receive.

Comment 13

[:gerard-majax]

(In reply to Jovan Gerodetti from comment #12)
> Google doesn't send a Content-Length so we can't know how much we will
> receive.

We could make use of Github release system to host it.

Comment 14

[Jovan Gerodetti]

(In reply to Alexandre LISSY :gerard-majax from comment #13)
> (In reply to Jovan Gerodetti from comment #12)
> > Google doesn't send a Content-Length so we can't know how much we will
> > receive.
> 
> We could make use of Github release system to host it.

but if we use GitHub to host it, we don't have a static URL to always point to the latest build :/

Comment 15

[:gerard-majax]

(In reply to Jovan Gerodetti from comment #14)
> (In reply to Alexandre LISSY :gerard-majax from comment #13)
> > (In reply to Jovan Gerodetti from comment #12)
> > > Google doesn't send a Content-Length so we can't know how much we will
> > > receive.
> > 
> > We could make use of Github release system to host it.
> 
> but if we use GitHub to host it, we don't have a static URL to always point
> to the latest build :/

Of course we do, we can name the file as we want with the releases :)

Comment 16

[Jovan Gerodetti]

(In reply to Alexandre LISSY :gerard-majax from comment #15)
> (In reply to Jovan Gerodetti from comment #14)
> > (In reply to Alexandre LISSY :gerard-majax from comment #13)
> > > (In reply to Jovan Gerodetti from comment #12)
> > > > Google doesn't send a Content-Length so we can't know how much we will
> > > > receive.
> > > 
> > > We could make use of Github release system to host it.
> > 
> > but if we use GitHub to host it, we don't have a static URL to always point
> > to the latest build :/
> 
> Of course we do, we can name the file as we want with the releases :)

but the URL is always:
https://github.com/mozilla-b2g/b2g-installer-builds/releases/download/[RELEASE TITLE]/[FILE NAME].zip

and we can't use the same release title twice :) For aries you also had to manually update the url in the builds.json