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

Introduce a HookOrder annotation to order hooks #521

Merged
merged 2 commits into from
Apr 11, 2023

Conversation

jtnord
Copy link
Member

@jtnord jtnord commented Apr 11, 2023

Introduce a HookOrder that allows the hooks to be run in an order not determined by their classname.

Using classname mean that external hooks would need to be put in multiple packages depending on if they needed to come before or after a given hook from OSS - and it also makes it possible to use better names for hooks in OSS.

Currently not needed but extracted from #510

  • 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 demonstrates feature works or fixes the issue

Introduce a HookOrder that allows the hooks to be run in an order not
determined by their classname.

Using classname mean that external hooks would need to be put in
multiple packages depending on if they needed to come before or after a
given hook from OSS - and it also makes it possible to use better names
for hooks in OSS.

Currently not needed but extracted from jenkinsci#510
@jtnord jtnord requested a review from a team as a code owner April 11, 2023 19:01
@basil basil changed the title Introduce a HookOrder annotation to order hooks Introduce a HookOrder annotation to order hooks Apr 11, 2023
@basil basil merged commit eb32afe into jenkinsci:master Apr 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants