Closed Bug 1072590 Opened 10 years ago Closed 10 years ago

Add the mapping to the b2g symbol mount on the symbolapi server for B2G breakpad symbols

Categories

(Firefox OS Graveyard :: Infrastructure, defect)

All
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: wcosta, Unassigned)

References

Details

User Story

With Bug 1061801 landed, profile.sh can now request symbols to symbol.api server.

The symbolSources field is set to ["B2G", "Firefox"] folder, so a mapping should be added in the symbol server.
      No description provided.
Vladan can you help us or let us know how to get this change deployed to symbolapi.mozilla.org?
Flags: needinfo?(vdjeric)
(In reply to Benoit Girard (:BenWa) from comment #1)
> Vladan can you help us or let us know how to get this change deployed to
> symbolapi.mozilla.org?

To deploy this change, you just need an IT bug asking them to make the config change and restart the server. Sample IT bug: bug 849708

For the config change, you need to add an extra line to the [SymbolPaths] section:

B2G = /mnt/netapp/breakpad/symbols_b2g

Wander, have you tested this config change on a real server with the Breakpad symbol mount? If not, I can help you with that
Flags: needinfo?(vdjeric) → needinfo?(wcosta)
(In reply to Vladan Djeric (:vladan) from comment #2)
> (In reply to Benoit Girard (:BenWa) from comment #1)
> > Vladan can you help us or let us know how to get this change deployed to
> > symbolapi.mozilla.org?
> 
> To deploy this change, you just need an IT bug asking them to make the
> config change and restart the server. Sample IT bug: bug 849708
> 
> For the config change, you need to add an extra line to the [SymbolPaths]
> section:
> 
> B2G = /mnt/netapp/breakpad/symbols_b2g
> 
> Wander, have you tested this config change on a real server with the
> Breakpad symbol mount? If not, I can help you with that

Yes, I did, I tested it on a local server.
Flags: needinfo?(wcosta)
Depends on: 1074174
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.