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

datadog-agent/7.64.1 package update #47515

Merged
merged 4 commits into from
Mar 20, 2025

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Mar 20, 2025

@octo-sts octo-sts bot added request-version-update request for a newer version of a package automated pr P1 This label indicates our scanning found High, Medium or Low CVEs for these packages. labels Mar 20, 2025
Copy link
Contributor Author

octo-sts bot commented Mar 20, 2025

⚠️ EXPERIMENTAL

Please use 👍 or 👎 on this comment to indicate if you agree or disagree with the recommendation.

To provide more detailed feedback please comment on the recommendation prefixed with /ai-verify:

e.g. /ai-verify partially helpful but I also added bash to the build environment

Gen AI suggestions to solve the build error:

Based on the error message, I'll provide a specific analysis and fix:

• Detected Error:

[git checkout] FAIL expected commit eb1cc6cf7b6d521bda3a8d1529cfe952e5355e89 on 7.64.x, got 143b5e0bfc592627f6da8453e6a283020487828e

• Error Category: Version/Commit

• Failure Point: Git checkout step in datadog-agent-core-integrations subpackage

• Root Cause Analysis: The commit hash specified in the melange YAML (eb1cc6cf7b6d521bda3a8d1529cfe952e5355e89) doesn't match what's actually available on the 7.64.x branch (143b5e0bfc592627f6da8453e6a283020487828e)

• Suggested Fix:
Update the expected-commit hash in the datadog-agent-core-integrations subpackage section:

- uses: git-checkout
  with:
    repository: https://github.com/DataDog/integrations-core
    branch: ${{vars.datadog-major-minor-x}}
    expected-commit: 143b5e0bfc592627f6da8453e6a283020487828e  # Updated hash

• Explanation: The build is failing because the git checkout step is finding a different commit than what was expected. This typically happens when the upstream repository has been updated. The fix updates the expected commit hash to match what's actually on the 7.64.x branch.

• Additional Notes:

  • The commit hash mismatch suggests the integrations-core repository has been updated since the last package build
  • This is a common occurrence when tracking branches instead of tags
  • The new commit hash was obtained from the error message showing the actual current commit

References:

@octo-sts octo-sts bot added the ai/skip-comment Stop AI from commenting on PR label Mar 20, 2025
@amberarcadia amberarcadia self-assigned this Mar 20, 2025
@OddBloke OddBloke force-pushed the wolfictl-ca39782b-eacf-41db-be24-8c8cc050202d branch from d3948d5 to d0bb32a Compare March 20, 2025 14:14
@octo-sts octo-sts bot added bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. manual/review-needed labels Mar 20, 2025
@OddBloke OddBloke requested a review from a team March 20, 2025 16:05
@OddBloke OddBloke enabled auto-merge March 20, 2025 16:05
@OddBloke OddBloke merged commit c789737 into main Mar 20, 2025
21 checks passed
@OddBloke OddBloke deleted the wolfictl-ca39782b-eacf-41db-be24-8c8cc050202d branch March 20, 2025 17:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ai/skip-comment Stop AI from commenting on PR automated pr bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. manual/review-needed P1 This label indicates our scanning found High, Medium or Low CVEs for these packages. request-version-update request for a newer version of a package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants