Skip to content

Conversation

michalvavrik
Copy link
Member

Summary

This should increase a chance that the daily build of this framework is tested with the latest Quarkus which is scheduled to be built after midnight quarkusio/quarkus#48054. It may not be always the case because the daily build of this framework takes more than 2 hours and I don't want to have big overlap with the Quarkus QE Test Suite daily build scheduled after 2:30 AM quarkus-qe/quarkus-test-suite#2479. We can't take these times literally because runs are not triggered immediately and we can't be sure how long we need before artifacts are available.

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
  • 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

@michalvavrik michalvavrik requested a review from rsvoboda May 27, 2025 11:52
@rsvoboda rsvoboda merged commit e967ef0 into quarkus-qe:main May 27, 2025
1 check passed
@michalvavrik michalvavrik deleted the feature/move-daily-build-after-upstream branch May 27, 2025 11:54
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