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

[1.4.z] Reduce log size in CI runs #1257

Merged

Conversation

gtroitsk
Copy link
Member

@gtroitsk gtroitsk commented Aug 26, 2024

Summary

Backports #1255 with some files exclusion

Please check the relevant options

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Dependency update
  • Refactoring
  • Backport
  • Release (follows conventions described in the RELEASE.md)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • This change requires a documentation update
  • This change requires execution against OCP (use run tests phrase in comment)

Checklist:

  • Example scenarios has been updated / added
  • Methods and classes used in PR scenarios are meaningful
  • Commits are well encapsulated and follow the best practices

@gtroitsk gtroitsk changed the title Reduce log size in CI runs [1.4.z] Reduce log size in CI runs Aug 26, 2024
(cherry picked from commit 1806bf9)
@gtroitsk gtroitsk force-pushed the backport/1.4-reduce-log-size branch from 14a8f92 to f1a2820 Compare August 29, 2024 16:44
@gtroitsk gtroitsk marked this pull request as ready for review August 30, 2024 07:06
@gtroitsk gtroitsk requested a review from michalvavrik August 30, 2024 07:08
@michalvavrik michalvavrik merged commit f44b89a into quarkus-qe:1.4.z Aug 30, 2024
7 checks passed
@gtroitsk gtroitsk deleted the backport/1.4-reduce-log-size branch August 30, 2024 07:37
@gtroitsk gtroitsk mentioned this pull request Sep 2, 2024
11 tasks
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