-
Notifications
You must be signed in to change notification settings - Fork 32
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
Use BOM, and adapt to a change in GitSCM behavior #78
Conversation
spotbugs issues on new core / spotbugs FTR |
Yeah I know, I will fix shortly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
I assume this was an unavoidable break unless I left the @DataBoundConstructor
of the GitSCM class unmodified. The change for the @DataBoundConstructor
makes the Pipeline syntax clearer and removes an ancient undocumented experimental git plugin code.
@jglick instead of supersedes block. Consider using the keywords in the description
|
I know about that, but it is unnecessary for Dependabot since it will automatically close superseded PRs. |
Right 😅 Didn't check the PRs just saw the block and thought phew forgetting to close the PRs would create noise my bad for interjecting. |
@car-roll could we get a release of this, to unblock |
Guess not. This is the kind of plugin that would be a good candidate for JEP-229… |
Noticed in jenkinsci/bom#431 that jenkinsci/git-plugin#1043 broke a longstanding test here (which ultimately should probably be rewritten to use some mock describables). Switching to the BOM and just temporarily overriding the
git
plugin version. Supersedes #58, #73, #74, #76, and #77.