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

internal/apps: better tagging #2425

Merged
merged 3 commits into from
Dec 12, 2023

Conversation

felixge
Copy link
Member

@felixge felixge commented Dec 12, 2023

What does this PR do?

  • Automatically add a trigger:weekly or trigger:nightly tag to scheduled test-app runs
  • Allow specifying custom DD_TAGS when manually triggering test-app runs
  • Switch from using individual bool inputs for selecting the scenarios to supplying them via JSON (because I ran into a GH Actions limitation, see commit message 😠)
  • Clean up some unrelated stuff (pr_default option)
Before After
CleanShot 2023-12-12 at 11 41 06@2x

CleanShot 2023-12-12 at 11 41 53@2x

Motivation

Make it easier to find the data for nightly, weekly and manually triggered test-app runs in the trace explorer and profile search.

Reviewer's Checklist

  • Changed code has unit tests for its functionality at or near 100% coverage.
  • System-Tests covering this feature have been added and enabled with the va.b.c-dev version tag.
  • There is a benchmark for any new code, or changes to existing code.
  • If this interacts with the agent in a new way, a system test has been added.
  • Add an appropriate team label so this PR gets put in the right place for the release notes.

For Datadog employees:

  • If this PR touches code that handles credentials of any kind, such as Datadog API keys, I've requested a review from @DataDog/security-design-and-guidance.
  • This PR doesn't touch any of that.

Unsure? Have a question? Request a review!

We are not running the test apps on PRs anymore, so there is no way to
invoke the jobs without either the workflow_call or workflow_dispatch
inputs being available. So we need no pr_default values to fall back to.
@pr-commenter
Copy link

pr-commenter bot commented Dec 12, 2023

Benchmarks

Benchmark execution time: 2023-12-12 10:03:08

Comparing candidate commit 90dc5d5 in PR branch felix.geisendoerfer/PROF-8773-better-tagging with baseline commit aada6eb in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 41 metrics, 0 unstable metrics.

Work around the fact that workflow_dispatch triggers can only have a
maximum of 10 inputs, ugh. See links below for more info.

- https://github.com/DataDog/dd-trace-go/actions/runs/7179140710
- https://github.com/orgs/community/discussions/8774
@felixge felixge force-pushed the felix.geisendoerfer/PROF-8773-better-tagging branch from 028614c to 90dc5d5 Compare December 12, 2023 09:47
@felixge felixge changed the title Felix.geisendoerfer/prof 8773 better tagging internal/apps: better tagging Dec 12, 2023
@felixge felixge marked this pull request as ready for review December 12, 2023 10:44
@felixge felixge requested a review from a team as a code owner December 12, 2023 10:44
@felixge felixge enabled auto-merge (squash) December 12, 2023 10:44
@felixge felixge merged commit 5b8cbdc into main Dec 12, 2023
62 of 63 checks passed
@felixge felixge deleted the felix.geisendoerfer/PROF-8773-better-tagging branch December 12, 2023 10:48
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.

2 participants