Skip to content

Ban JUnit 4 imports #142

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Aug 17, 2025
Merged

Ban JUnit 4 imports #142

merged 1 commit into from
Aug 17, 2025

Conversation

@MarkEWaite
Copy link
Contributor

Ban JUnit 4 imports

All tests in the plugin are using JUnit 5.

Testing done

Confirmed automated tests pass.

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests that demonstrate the feature works or the issue is fixed
@MarkEWaite
Ban JUnit 4 imports
a6f0bbb 
All tests in the plugin are using JUnit 5.
@MarkEWaite MarkEWaite added the chore Reduces maintenance effort by changes not directly visible to users label Aug 17, 2025
@MarkEWaite MarkEWaite requested a review from a team as a code owner August 17, 2025 12:19
@MarkEWaite MarkEWaite added the chore Reduces maintenance effort by changes not directly visible to users label Aug 17, 2025
@MarkEWaite MarkEWaite merged commit 66935fe into jenkinsci:master Aug 17, 2025
17 checks passed
@MarkEWaite MarkEWaite deleted the ban-junit-4-tests branch August 17, 2025 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chore Reduces maintenance effort by changes not directly visible to users

1 participant

@MarkEWaite