Skip to content
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 build instrumentation API #2612

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

williamjallen
Copy link
Collaborator

@williamjallen williamjallen commented Dec 3, 2024

This PR replaces the initial build instrumentation work in #2460 with a more complete version based on a working CMake/CTest implementation. See #2395 for the full feature request.

I plan to make a follow-up PR to add support for configure measurements once a handful of blocking database schema changes are completed. Future PRs will also implement various UIs to display the data collected here.

@williamjallen williamjallen added this to the v3.7 milestone Dec 3, 2024
@williamjallen williamjallen marked this pull request as draft December 3, 2024 21:26
@williamjallen williamjallen changed the title Add build instrumentation handling logic Add build instrumentation API Dec 15, 2024
@williamjallen williamjallen force-pushed the build-instrumentation branch 2 times, most recently from a4106b9 to 9128d2d Compare December 17, 2024 15:38
@williamjallen williamjallen modified the milestones: v3.7, v3.8 Jan 2, 2025
@williamjallen williamjallen force-pushed the build-instrumentation branch 2 times, most recently from ee592af to 9811123 Compare January 15, 2025 13:21
@williamjallen williamjallen modified the milestones: v3.8, v3.9 Jan 28, 2025
github-merge-queue bot pushed a commit that referenced this pull request Feb 17, 2025
This PR pulls out some of the logic in
#2612 for matching full XML paths
into a separate PR in anticipation of several upcoming PRs. By
specifying the full XML path for an element, the exact element being
targeted is more clear. For the sake of example, I used the new path
method to locate all of the `<Site>` elements.
@williamjallen williamjallen force-pushed the build-instrumentation branch 6 times, most recently from 6fe8a11 to 02f18e7 Compare February 28, 2025 16:02
@williamjallen williamjallen modified the milestones: v3.9, v4.0 Feb 28, 2025
@williamjallen williamjallen force-pushed the build-instrumentation branch 2 times, most recently from 78a147b to 0d9f57f Compare March 2, 2025 01:26
@williamjallen williamjallen marked this pull request as ready for review March 2, 2025 02:11
Copy link
Member

@josephsnyder josephsnyder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! once the data was properly added into the database, it made sense and was able to be pulled out in GraphQL. As discussed F2F, I'm not a big fan of command and commands being attributes on the build but I'm not willing to let that stop this from moving forward

@williamjallen williamjallen force-pushed the build-instrumentation branch from 0d9f57f to e7d81a8 Compare March 21, 2025 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants