-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add debugging symbols to build #1810
Comments
I don't think that would be appropriate; rebuilding the image with debugging symbols for the specific module that is giving issues (if needed) would be better. Or use |
Testing on an individual basis, that makes perfect sense. The idea would be to run in a CI/CD pipeline continuously, so having debugging symbols available in the image would be the ideal. We could possibly have a separate image build for these purposes. @polvi might be able to explain better as this is well outside my wheelhouse. This stems from a request to build out testing infrastructure that regularly runs test datasets through the pipeline. |
A separate image would work too. |
Cool. We can do that. |
I have someone helping with a testing environment for running test datasets through the pipeline when there are changes to the code base, a bit CI/CD style. @pierotofy: Is it appropriate or problematic to add debugging symbols to the default docker builds to facilitate this?
The text was updated successfully, but these errors were encountered: