/api/ProductVersions/

[Peter Bengtsson]

Last week we launched a new API endpoint
https://crash-stats.mozilla.com/api/#ProductVersions

It's your best place for all things related to products and versions.
It replaces all three of /api/CurrentProducts, /api/CurrentVersions and
(seemingly similar) /api/ProductsVersions
In fact, these old ones continue to exist but they're now just, under the
hood, re-packagings of calls to /api/ProductVersions.

If in doubt, ping peterbe#breakpad

--
Peter Bengtsson
Mozilla Tools & Services

[Benjamin Smedberg]

Can you describe how to use this? I created a query that I thought would
ask for the 46 betas, but that doesn't appear to have worked:

https://crash-stats.mozilla.com/api/ProductVersions/?end_date=2016-04-10&product=Firefox&start_date=2016-03-01&version=46.0

Does this API give any detail for nightly/aurora builds, or just
beta/release?

--BDS

On Tue, Apr 5, 2016 at 11:15 AM, Peter Bengtsson <pbeng...@mozilla.com>
wrote:

--
Benjamin Smedberg
Engineering Manager, Firefox

[Robert Kaiser]

Liz Henry (:lizzard) schrieb:
> So this this to replace or improve on queries like the crashes per day
> one?

It's basically unrelated, this thread is just about an API on how the UI
(and things like my external reports) get information from the Socorro
backend about which versions exist.

KaiRo

[Chris Hofmann]

Yeah, definitely would help thing to do version filtering, and/or maybe add
notes on the page that specify the format expected for exact matches.

Can you also do better character conversion?

Try

*https://crash-stats.mozilla.com/api/CommentsBySignature/?signature=mozilla::dom::MediaSource::Duration
<https://crash-stats.mozilla.com/api/CommentsBySignature/?signature=mozilla::dom::MediaSource::Duration>*
to see comment results that are largely in languages with extended
character sets.

Having the ability to take that output and pump it into something like
google translate with auto detection on input language could be quite
handy.

Bonus points for an option to just return the comments and filter out crash
id and report date that could confuse auto translation with lots of english
and extra gibberish.

-chofmann


On Tue, Apr 5, 2016 at 8:52 AM, Peter Bengtsson <pbeng...@mozilla.com>
wrote:

> The version string has to be exact.
> I.e.
> https://crash-stats.mozilla.com/api/ProductVersions/?product=Firefox&version=46.0
> yields nothing.
>
>
> The main use of this API endpoint is in the webapp, as foundation for
> other stuff such as Crash per User and there we don't filter by version
> like that.
> If there's a strong need for ability to do something like `&version=46.0*`
> we can work on that.
>
> I just noticed that there's no way, in this API, to query by build type.
> That data is in there. E.g.
> https://gist.github.com/peterbe/e97b7b70c335f212f171b9c1aafea187
>
> Perhaps instead of adding some regex hack to the version string, I'll just
> add the ability to filter by build_type. E.g. &build_type=beta
> I can do that if you think it'll help.

[Robert Kaiser]

It's more a "what we've built" than a "what we've shipped" as it doesn't
know if we actually released those builds yet, but if that's what they
need, it could be helpful.
Otherwise, i.e. if they need to know what actually shipped, something
like the product-details stuff would be more helpful.

This API here is very much geared towards what crash-stats requires, I'm
not sure how useful it it outside of that.

There are thoughts about creating a more generic build/release database,
but I think no concrete work yet.

KaiRo

Liz Henry (:lizzard) schrieb:

> That sounds potentially useful for the metrics team to use for their
> canonical "what we've shipped" product list. I know Ali was looking for
> that from relman. I'll let him know.

[Peter Bengtsson]

[Peter Bengtsson]

We basically scrape https://archives.mozilla.org and through myriad maze of
stored procedures and legacy business logic we populate a database table
with what we've scraped. Then that's exposed on a web API URL in JSON
format. It actually has nothing to do with crashes. Just a reflection of
which products and versions we're "prepared" for.

On Tue, Apr 5, 2016 at 2:29 PM, Liz Henry (:lizzard) <ehe...@mozilla.com>
wrote:

> That sounds potentially useful for the metrics team to use for their
> canonical "what we've shipped" product list. I know Ali was looking for
> that from relman. I'll let him know.
>
> On Tue, Apr 5, 2016 at 9:34 AM, Robert Kaiser <ka...@mozilla.com> wrote:
>
>> Liz Henry (:lizzard) schrieb:
>>
>>> So this this to replace or improve on queries like the crashes per day
>>> one?
>>>
>>
>> It's basically unrelated, this thread is just about an API on how the UI
>> (and things like my external reports) get information from the Socorro
>> backend about which versions exist.
>>
>> KaiRo
>>
>
>
>

> --
> ----
> Liz Henry (:lizzard)
> Firefox Release Manager
> lhe...@mozilla.com

[Peter Bengtsson]

On Tue, Apr 5, 2016 at 3:29 PM, Robert Kaiser <ka...@mozilla.com> wrote:

> It's more a "what we've built" than a "what we've shipped" as it doesn't
> know if we actually released those builds yet, but if that's what they
> need, it could be helpful.
> Otherwise, i.e. if they need to know what actually shipped, something like
> the product-details stuff would be more helpful.
>
> This API here is very much geared towards what crash-stats requires, I'm
> not sure how useful it it outside of that.
>
> There are thoughts about creating a more generic build/release database,
> but I think no concrete work yet.
>
>

That work - i.e. stop scraping HTML on archives.mozilla.org - got a lot of
thought/planning momentum in Mozlando but we're up against some blockers in
how RelEng does things with TaskCluster. In fact, there's some element of
them getting entirely out of Buildbot. And there was the issue about
lifting a beta to release which isn't a pure build but nevertheless a piece
of information we need.

Not sure what the status is. Chris?

I think the idea is that when the RelEng team finishes their TaskCluster
magic our team will be able to listen to Pulse and suck up all the same
information.
How we store that and whether that stored metadata is a Socorro thing or
not we have not decided.



> KaiRo

>
>
>
> Liz Henry (:lizzard) schrieb:
>
>> That sounds potentially useful for the metrics team to use for their
>> canonical "what we've shipped" product list. I know Ali was looking for
>> that from relman. I'll let him know.
>>
>> On Tue, Apr 5, 2016 at 9:34 AM, Robert Kaiser <ka...@mozilla.com> wrote:
>>
>> Liz Henry (:lizzard) schrieb:
>>>
>>> So this this to replace or improve on queries like the crashes per day
>>>> one?
>>>>
>>>> It's basically unrelated, this thread is just about an API on how the UI
>>> (and things like my external reports) get information from the Socorro
>>> backend about which versions exist.
>>>
>>> KaiRo
>>>
>>>
>>
>>
>


--

[Lawrence Mandel]

On Wed, Apr 6, 2016 at 9:03 AM, Peter Bengtsson <pbeng...@mozilla.com>
wrote:

>
>

> On Tue, Apr 5, 2016 at 3:29 PM, Robert Kaiser <ka...@mozilla.com> wrote:
>
>> It's more a "what we've built" than a "what we've shipped" as it doesn't
>> know if we actually released those builds yet, but if that's what they
>> need, it could be helpful.
>> Otherwise, i.e. if they need to know what actually shipped, something
>> like the product-details stuff would be more helpful.
>>
>> This API here is very much geared towards what crash-stats requires, I'm
>> not sure how useful it it outside of that.
>>
>> There are thoughts about creating a more generic build/release database,
>> but I think no concrete work yet.
>>
>>
> That work - i.e. stop scraping HTML on archives.mozilla.org - got a lot
> of thought/planning momentum in Mozlando but we're up against some blockers
> in how RelEng does things with TaskCluster. In fact, there's some element
> of them getting entirely out of Buildbot. And there was the issue about
> lifting a beta to release which isn't a pure build but nevertheless a piece
> of information we need.
>
> Not sure what the status is. Chris?
>
> I think the idea is that when the RelEng team finishes their TaskCluster
> magic our team will be able to listen to Pulse and suck up all the same
> information.
> How we store that and whether that stored metadata is a Socorro thing or
> not we have not decided.
>

Sylvestre has also been working on an API for ship-it that will make it
easy to query for current and past release data including version, channel,
and date. I'm sure he can add more data depending on what's needed.

Lawrence

>
>
>
>> KaiRo
>>
>>
>>
>> Liz Henry (:lizzard) schrieb:
>>
>>> That sounds potentially useful for the metrics team to use for their
>>> canonical "what we've shipped" product list. I know Ali was looking for
>>> that from relman. I'll let him know.
>>>
>>> On Tue, Apr 5, 2016 at 9:34 AM, Robert Kaiser <ka...@mozilla.com> wrote:
>>>
>>> Liz Henry (:lizzard) schrieb:
>>>>
>>>> So this this to replace or improve on queries like the crashes per day
>>>>> one?
>>>>>
>>>>> It's basically unrelated, this thread is just about an API on how the
>>>> UI
>>>> (and things like my external reports) get information from the Socorro
>>>> backend about which versions exist.
>>>>
>>>> KaiRo
>>>>
>>>>
>>>
>>>
>>
>
>
> --
> Peter Bengtsson
> Mozilla Tools & Services
>

> _______________________________________________
> Stability mailing list
> Stab...@mozilla.org
> https://mail.mozilla.org/listinfo/stability
>
>

[Peter Bengtsson]

Landed in stage and will be in production later this week.

You can now filter by appending
&build_type=(aurora|beta|esr|nightly|release)

Note that this feel accepts a list that get's OR'ed. I.e.
`...&build_type=beta&build_type=aurora` means productversions that are
either beta OR aurora.
E.g.
https://crash-stats.allizom.org/api/ProductVersions/?product=Firefox&active=True&build_type=beta&build_type=aurora

On Tue, Apr 5, 2016 at 11:32 AM, Benjamin Smedberg <bsme...@mozilla.com>
wrote:

> Can you describe how to use this? I created a query that I thought would
> ask for the 46 betas, but that doesn't appear to have worked:
>
>
> https://crash-stats.mozilla.com/api/ProductVersions/?end_date=2016-04-10&product=Firefox&start_date=2016-03-01&version=46.0
>
> Does this API give any detail for nightly/aurora builds, or just
> beta/release?
>
> --BDS
>

> On Tue, Apr 5, 2016 at 11:15 AM, Peter Bengtsson <pbeng...@mozilla.com>
> wrote:
>
>> Last week we launched a new API endpoint
>> https://crash-stats.mozilla.com/api/#ProductVersions
>>
>> It's your best place for all things related to products and versions.
>> It replaces all three of /api/CurrentProducts, /api/CurrentVersions and
>> (seemingly similar) /api/ProductsVersions
>> In fact, these old ones continue to exist but they're now just, under the
>> hood, re-packagings of calls to /api/ProductVersions.
>>
>> If in doubt, ping peterbe#breakpad
>>

>> --
>> Peter Bengtsson
>> Mozilla Tools & Services
>>
>
>
>

> --
> Benjamin Smedberg
> Engineering Manager, Firefox
>
>