Closed
Bug 1149012
Opened 10 years ago
Closed 9 years ago
Capture additional build information to support system logging
Categories
(Firefox OS Graveyard :: Gaia::Bugzilla Lite, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jgong, Unassigned)
References
Details
Need to be able to capture build information to support bug system logging for bugzilla lite.
The Build Information to capture are:
- Gaia-Rev
- Gecko-Rev
- Build-ID
- Version
- Device-Name eg. Z3
- Base image
Reporter | ||
Updated•10 years ago
|
Assignee: nobody → dale
Comment 1•10 years ago
|
||
I can probably pull these in Gaia since they are displayed in the settings app, it doesnt look like these exist in the current information we pull, but want to check before working on it. Alexandre we dont already have this information right?
Flags: needinfo?(lissyx+mozillians)
Comment 2•10 years ago
|
||
Actually, this is going to need to be done in Gecko, trying to pull that data inside Bugzilla Lite would require it being a certified app and very much want this to be an actual real web app
Comment 3•10 years ago
|
||
(In reply to Jean Gong from comment #0)
> Need to be able to capture build information to support bug system logging
> for bugzilla lite.
> The Build Information to capture are:
> - Gaia-Rev
> - Gecko-Rev
> - Build-ID
> - Version
> - Device-Name eg. Z3
> - Base image
We already have all of those, between application.ini and properties. Except Gaia commit, since it's not easily accessible (gaia_commit.txt burried in the Settings app).
Flags: needinfo?(lissyx+mozillians)
Comment 4•10 years ago
|
||
Here is an example of what gets dumped
Comment 5•10 years ago
|
||
see https://github.com/Mozilla-TWQA/B2G-flash-tool/blob/master/check_versions.py
I think the script captures everything, if we can get the output into the bug that would be awesome.
Comment 8•10 years ago
|
||
Not currently working on this, hoping to launch v2 asap so I can be working on the same branch
Assignee: dale → nobody
Hey Dale, carrying on the conversation; The main thing that is missing from the logs is :
1) Gaia-Rev, it's in the application.zip resources/gaia_commit.txt which isn't part of the logging information.
Also I came to realize that we only get this information if they submit a logcat/logshake.
How do we get this information in the bug in general? Otherwise it's going to be really tough to triage the bugs when we get things like "It crashed." bug 812697 shows that we have to do a back and forth a little in order to get more information to try to reproduce the bug.
![]() |
||
Updated•10 years ago
|
Flags: needinfo?(dale)
Comment 10•10 years ago
|
||
Hey
So we would like to have bugzilla lite be able to pick up some version information from the currently running gaia / gecko and gonk, right now we send over some config files when you trigger a bug via logshake, however it isnt currently ideal since 1. only bugs created via logshake get this information, 2. the logshake information is full of fairly private data.
It would be fairly easy to pick this stuff up in settings, but very against making this a certified application
Flags: needinfo?(jonas)
Flags: needinfo?(fabrice)
Flags: needinfo?(dale)
Comment 11•10 years ago
|
||
(In reply to Dale Harvey (:daleharvey) from comment #10)
> Hey
>
> So we would like to have bugzilla lite be able to pick up some version
> information from the currently running gaia / gecko and gonk, right now we
> send over some config files when you trigger a bug via logshake, however it
> isnt currently ideal since 1. only bugs created via logshake get this
> information, 2. the logshake information is full of fairly private data.
>
> It would be fairly easy to pick this stuff up in settings, but very against
> making this a certified application
I have always wondered why is the Gaia version not stored into a settings, instead of being burried into a file ... That would not solve it for Bz Lite, since Settings API is certified-only. We have it opened for privileged apps but only on a reduced set of values (currently, wallpaper only). Maybe we could include Gecko and Gaia commit ?
ni dale in regards to https://bugzilla.mozilla.org/show_bug.cgi?id=1149012#c11
Flags: needinfo?(dale)
Comment 13•10 years ago
|
||
Yeh publically accessible settings (or navigator properties) would be fine but would definitely need some input from Jonas or maybe Ehsan about that.
Basically we would like the Gaia + Gecko commit, possible the OS version accessible ideally from a plain web app, this app will commonly be installed though so it could be behind an app and we can fallback gracefully (not include those details when not installed)
Flags: needinfo?(dale) → needinfo?(ehsan)
Comment 14•10 years ago
|
||
I have no good idea on how to expose that to unprivileged content without doing something awful like changing the UA string.
Flags: needinfo?(fabrice)
Comment 15•10 years ago
|
||
(In reply to Dale Harvey (:daleharvey) from comment #13)
> Yeh publically accessible settings (or navigator properties) would be fine
> but would definitely need some input from Jonas or maybe Ehsan about that.
>
> Basically we would like the Gaia + Gecko commit, possible the OS version
> accessible ideally from a plain web app, this app will commonly be installed
> though so it could be behind an app and we can fallback gracefully (not
> include those details when not installed)
I don't really know what bugzilla lite is, and what we're doing here. We don't usually expose this information to all web pages. If this is a privileged app, it can probably read at least some of things from the settings database, but I don't know how this information is stored there.
Flags: needinfo?(ehsan)
We support privileged apps using settings these days. You just have to add the specific setting to PermissionTable.jsm
So adding a setting that specifically contains the build info sounds like a workable, though hacky, but simple, solution.
Flags: needinfo?(jonas)
Comment 17•9 years ago
|
||
No longer in scope
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•