Skip to content

Conversation

@scotthart
Copy link
Member

No description provided.

@gemini-code-assist
Copy link

Summary of Changes

Hello @scotthart, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly upgrades and refines the Continuous Integration (CI) infrastructure, with a particular focus on Windows builds. It modernizes the dependency management by updating vcpkg and deeply integrating the OpenTelemetry C++ library, ensuring builds consistently use C++17. The changes address specific platform compatibility issues and streamline the process of incorporating external libraries, leading to more robust and reliable CI pipelines.

Highlights

  • Vcpkg and OpenTelemetry Updates: The vcpkg baseline has been updated to a newer commit, and the OpenTelemetry C++ library integration has been significantly enhanced through new vcpkg overlay ports. This includes updating the OpenTelemetry Protocol (OTLP) version to 1.6.0 and adding new features like otlp-file and opentracing.
  • C++17 Standardization: The build process now explicitly enforces the C++17 standard across various CMake configurations, replacing previous C++14 settings. This ensures modern C++ features are utilized and consistent compilation standards are maintained.
  • Windows Build Improvements: Specific fixes and configurations have been applied to improve Windows builds. This includes adding -DNOMINMAX to prevent macro conflicts, adjusting path separators for vcpkg overlay ports, and ensuring proper OpenTracing linking on Windows platforms.
  • New Vcpkg Manifests: New vcpkg.json and portfile.cmake files have been introduced for opentelemetry-cpp within the vcpkg overlay directories for both GitHub Actions and Kokoro CI, standardizing its dependency management and feature definitions.
Ignored Files
  • Ignored by pattern: .github/workflows/** (2)
    • .github/workflows/test-runner.yml
    • .github/workflows/windows-cmake.yml
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the CI/CD configuration for Windows builds, primarily focusing on vcpkg and OpenTelemetry-CPP. Key changes include setting C++17 as the standard, updating vcpkg versions and SHA hashes, and introducing new features and fixes for OpenTelemetry-CPP dependencies. The changes improve Windows compatibility and dependency management.

endif ()

if (WIN32)
add_definitions(-DNOMINMAX)

Choose a reason for hiding this comment

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

high

Adding -DNOMINMAX is a crucial step for Windows compatibility in C++ projects. This prevents conflicts between the min/max macros defined in windows.h and std::min/std::max from the C++ standard library, which can lead to unexpected compilation errors or behavior.

args+=("-DVCPKG_TARGET_TRIPLET=${VCPKG_TRIPLET}")
fi
args+=("-DVCPKG_OVERLAY_PORTS=ci/gha/builds/vcpkg-overlays")
args+=("-DVCPKG_OVERLAY_PORTS=ci\gha\builds\vcpkg-overlays")

Choose a reason for hiding this comment

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

high

Changing the path separator from / to \ for VCPKG_OVERLAY_PORTS is essential for correct functionality on Windows systems, as Windows uses backslashes for directory paths. This ensures that vcpkg can correctly locate the overlay ports.

fi
local args
args=(
-DCMAKE_CXX_STANDARD=17

Choose a reason for hiding this comment

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

medium

Setting CMAKE_CXX_STANDARD to 17 explicitly ensures that the project is built with C++17 features. This is a good practice for modern C++ development and aligns with the repository's stated support for C++14 as a minimum version, effectively upgrading the standard used in this build configuration.

References
  1. The repository style guide states that C++14 is the minimum supported C++ standard version. Upgrading to C++17 is a positive step towards modern C++ practices. (link)

"-DgRPC_CPP_PLUGIN_EXECUTABLE=${CURRENT_HOST_INSTALLED_DIR}/tools/grpc/grpc_cpp_plugin${VCPKG_HOST_EXECUTABLE_SUFFIX}"
)
endif ()
list(APPEND FEATURE_OPTIONS -DCMAKE_CXX_STANDARD=17 -DWITH_STL=CXX17)

Choose a reason for hiding this comment

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

medium

Explicitly setting CMAKE_CXX_STANDARD=17 and WITH_STL=CXX17 ensures consistency in the C++ standard used for the OpenTelemetry-CPP port. This aligns with modern C++ practices and the project's C++ standard requirements.

References
  1. The repository style guide states that C++14 is the minimum supported C++ standard version. Using C++17 here is an appropriate upgrade. (link)

WITH_USER_EVENTS
BUILD_TRACEPOINTS)
BUILD_TRACEPOINTS
gRPC_CPP_PLUGIN_EXECUTABLE)

Choose a reason for hiding this comment

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

medium

Adding gRPC_CPP_PLUGIN_EXECUTABLE to MAYBE_UNUSED_VARIABLES is a good practice to prevent CMake warnings about unused variables, which can help keep the build output clean and focused on actual issues.

@codecov
Copy link

codecov bot commented Jan 31, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.86%. Comparing base (e790ce9) to head (7243646).

Additional details and impacted files
@@                  Coverage Diff                   @@
##           prepare-for-v3.0.0   #15924      +/-   ##
======================================================
+ Coverage               92.85%   92.86%   +0.01%     
======================================================
  Files                    2343     2343              
  Lines                  216258   216258              
======================================================
+ Hits                   200804   200835      +31     
+ Misses                  15454    15423      -31     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant