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

Update Node.js GitHub action to use npm lockfile, switch to latest Jaeger UI #6074

Merged

Conversation

andreasgerstmayr
Copy link
Contributor

@andreasgerstmayr andreasgerstmayr commented Oct 10, 2024

Which problem is this PR solving?

  • Update Node.js GitHub action to use npm lockfile, switch to latest Jaeger UI

Description of the changes

How was this change tested?

Checklist

…eger UI

Required for: jaegertracing#2462
Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
@andreasgerstmayr andreasgerstmayr requested a review from a team as a code owner October 10, 2024 17:04
Copy link
Member

@yurishkuro yurishkuro left a comment

Choose a reason for hiding this comment

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

Good catch, thanks.

@yurishkuro yurishkuro added the changelog:ci Change related to continuous integration / testing label Oct 10, 2024
Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
Copy link

codecov bot commented Oct 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.93%. Comparing base (c7e9f3d) to head (8c7aa64).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6074      +/-   ##
==========================================
- Coverage   96.94%   96.93%   -0.02%     
==========================================
  Files         352      352              
  Lines       16717    16717              
==========================================
- Hits        16206    16204       -2     
- Misses        328      329       +1     
- Partials      183      184       +1     
Flag Coverage Δ
badger_v1 7.99% <ø> (ø)
badger_v2 1.84% <ø> (ø)
cassandra-4.x-v1 15.75% <ø> (ø)
cassandra-4.x-v2 1.77% <ø> (ø)
cassandra-5.x-v1 15.75% <ø> (ø)
cassandra-5.x-v2 1.77% <ø> (ø)
elasticsearch-6.x-v1 19.05% <ø> (-0.02%) ⬇️
elasticsearch-7.x-v1 19.11% <ø> (ø)
elasticsearch-8.x-v1 19.31% <ø> (-0.02%) ⬇️
elasticsearch-8.x-v2 1.83% <ø> (-0.02%) ⬇️
grpc_v1 9.36% <ø> (+0.01%) ⬆️
grpc_v2 7.12% <ø> (ø)
kafka-v1 9.69% <ø> (ø)
kafka-v2 1.84% <ø> (ø)
memory_v2 1.83% <ø> (-0.02%) ⬇️
opensearch-1.x-v1 19.16% <ø> (ø)
opensearch-2.x-v1 19.16% <ø> (ø)
opensearch-2.x-v2 1.84% <ø> (ø)
tailsampling-processor 0.49% <ø> (ø)
unittests 95.74% <ø> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
@yurishkuro yurishkuro enabled auto-merge (squash) October 11, 2024 16:41
@andreasgerstmayr
Copy link
Contributor Author

Let's hold off this PR until jaegertracing/jaeger-ui#2478 is merged.

auto-merge was automatically disabled October 14, 2024 16:06

Head branch was pushed to by a user without write access

@yurishkuro yurishkuro closed this Oct 14, 2024
@yurishkuro yurishkuro reopened this Oct 14, 2024
@andreasgerstmayr
Copy link
Contributor Author

Thanks for re-triggering the GitHub actions, the tests pass now (before I've seen docker rate limits, and before that a Node.js version mismatch in the hotrod workflow which I've fixed).

@yurishkuro yurishkuro merged commit 77939d4 into jaegertracing:main Oct 15, 2024
49 checks passed
chahatsagarmain pushed a commit to chahatsagarmain/jaeger that referenced this pull request Oct 23, 2024
yurishkuro added a commit to yurishkuro/jaeger that referenced this pull request Nov 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog:ci Change related to continuous integration / testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants