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

Backport of ci:upload test results to datadog into release/1.13.x #17297

Conversation

hc-github-team-consul-core
Copy link
Contributor

Backport

This PR is auto-generated from #17206 to be assessed for backporting due to the inclusion of the label backport/1.13.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@jmurret
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.


Description

Currently our workflow and job information is uploaded to datadog. Test information is not. This PR uploads the junit results file to DataDog.

Testing & Reproduction steps

  1. go to theupload coverage step of any test job.
  2. It will give you the below output and you can verify there. Example job is: https://github.com/hashicorp/consul/actions/runs/4916931172/jobs/8781403486?pr=17206
Run datadog-ci junit upload --service "$GITHUB_REPOSITORY" $TEST_RESULTS_DIR/results.xml
Starting upload with concurrency 20. 
Will upload jUnit XML file /tmp/test-results/results.xml
service: hashicorp/consul
Uploading jUnit XML test report file in /tmp/test-results/results.xml
✅ Uploaded [1](https://github.com/hashicorp/consul/actions/runs/4916931172/jobs/8781403486?pr=17206#step:12:1) files in 0.199 seconds.
Syncing git metadata...
[unshallow] Git repository is a shallow clone., unshallowing it...
[unshallow] Setting remote.origin.partialclonefilter to "blob:none" to avoid fetching file content
[unshallow] Running git fetch --shallow-since="1 month ago" --update-shallow --refetch
[unshallow] Fetch completed.
✅ Synced git metadata in 7.016 seconds.
=================================================================================================
* View detailed reports on Datadog (they can take a few minutes to become available)
* Commit report:
* https://app.datadoghq.com/ci/redirect/tests/https%3A%2F%2Fgithub.com%2Fhashicorp%2Fconsul.git/-/hashicorp%2Fconsul/-/jm%2FNET-3692/-/8642c685c7cd4[17](https://github.com/hashicorp/consul/actions/runs/4916931172/jobs/8781403486?pr=17206#step:12:18)8a1a963bf392f61fe4a9c437f?env=ci
* Test runs report:
* https://app.datadoghq.com/ci/test-runs?query=%[20](https://github.com/hashicorp/consul/actions/runs/4916931172/jobs/8781403486?pr=17206#step:12:21)%40ci.job.url%3A%[22](https://github.com/hashicorp/consul/actions/runs/4916931172/jobs/8781403486?pr=17206#step:12:23)https%3A%2F%2Fgithub.com%2Fhashicorp%2Fconsul%2Fcommit%2F8642c685c7cd4178a1a963bf392f61fe4a9c437f%2Fchecks%22
=================================================================================================

Links

PR Checklist

  • updated test coverage
  • external facing docs updated
  • appropriate backport labels added
  • not a security concern

Overview of commits

Copy link

Choose a reason for hiding this comment

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

Auto approved Consul Bot automated PR

@github-actions github-actions bot added theme/contributing Additions and enhancements to community contributing materials type/ci Relating to continuous integration (CI) tooling for testing or releases labels May 10, 2023
@jmurret
Copy link
Member

jmurret commented May 10, 2023

Closing in favor of #17300

@jmurret jmurret closed this May 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme/contributing Additions and enhancements to community contributing materials type/ci Relating to continuous integration (CI) tooling for testing or releases
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants