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

Draft
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.

The following items need to be resolved before this can be merged:

  • Submission tests need to be added
  • Support for subprojects needs to be added (measurements are currently associated with the parent build if subprojects are being used)
  • XML schema files need to be updated to reflect the new schema

I plan to make a follow-up PR to add support for configure measurements once a handful of blocking schema changes are completed.

@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.
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.

1 participant