Details
-
Task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
Description
Problem
From a given install (tarball, RPM, DEB) you only have the version information available, not the GitHash the binaries were built from.
Solution
Compile the following into the binaries
- GitHash the build was from
- Buildbot build number
This info should be available as
- system variable (e.g. VERSION_GITHASH) - Must
- from output of 'mysql -v' (but that's just the githash of mysql and not mysqld) - Should
- from output of 'mysqld --verbose --help' - Must
Rationale
Supportability. Given a random build a user may have, there is no simple mechanism to track back to the GitHash of the commit the code was built with. This is especially important for anybody with a custom build (e.g. feature testing, customer patch etc.).
Workaround
None
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Description |
h1. Problem
h1. Solution Compile the following into the binaries - GitHash the build was from - Buildbot build number This info should be available as - system variable (e.g. VERSION_GITHASH) - Must - from output of 'mysql -v' (but that's just the githash of mysql and not mysqld) - Should - from output of 'mysqld --verbose --help' - Must h1. Rationale Supportability. Given a random build a user may have, there is no simple mechanism to track back to the GitHash of the commit the code was built with. This is especially important for anybody with a custom build (e.g. feature testing, customer patch etc.). h1. Workaround None |
h1. Problem
From a given install (tarball, RPM, DEB) you only have the version information available, not the GitHash the binaries were built from. h1. Solution Compile the following into the binaries - GitHash the build was from - Buildbot build number This info should be available as - system variable (e.g. VERSION_GITHASH) - Must - from output of 'mysql -v' (but that's just the githash of mysql and not mysqld) - Should - from output of 'mysqld --verbose --help' - Must h1. Rationale Supportability. Given a random build a user may have, there is no simple mechanism to track back to the GitHash of the commit the code was built with. This is especially important for anybody with a custom build (e.g. feature testing, customer patch etc.). h1. Workaround None |
Fix Version/s | 10.3 [ 22126 ] |
Support case ID | 14007 | 14007 15247 |
Assignee | Julien Fritsch [ julien.fritsch ] |
Assignee | Julien Fritsch [ julien.fritsch ] |
Priority | Major [ 3 ] | Critical [ 2 ] |
Assignee | Vladislav Vaintroub [ wlad ] |
Fix Version/s | 10.3.2 [ 22533 ] | |
Fix Version/s | 10.3 [ 22126 ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 80457 ] | MariaDB v4 [ 133219 ] |
Zendesk Related Tickets | 184550 200877 |