[SERVER-28024] Generate deterministic buildIDs on platforms that support it Created: 15/Feb/17  Updated: 06/Dec/22  Resolved: 03/Feb/18

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Ramon Fernandez Marina Assignee: DO NOT USE - Backlog - Dev Tools
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Developer Tools
Sprint: Platforms 2017-04-17
Participants:

 Description   

If we were to generate deterministic buildIds (rather than letting the linker choose a UUID), we could more easily produce a manifest that explains which object a given buildId is for (SERVER-28023). This would help with any work/project around analyzing stack traces.



 Comments   
Comment by Andrew Morrow (Inactive) [ 03/Feb/18 ]

ramon.fernandez - Please feel free to re-open if you need something like this again in the future.

Comment by Andrew Morrow (Inactive) [ 03/Feb/18 ]

Per discussion in the associated ticket, we aren't doing this work.

Comment by Andrew Morrow (Inactive) [ 17/Feb/17 ]

SCons can generate the build IDs, and then, since it knows them already, emit a manifest without needing to extract the randomly generated ID with readelf.

Comment by Andy Schwerin [ 16/Feb/17 ]

Why does this make SERVER-28023 any easier?

Generated at Thu Feb 08 04:16:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.