-
Notifications
You must be signed in to change notification settings - Fork 20
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
Force the PR title/body if rerun #646
Comments
Makes sense definitely. Since we check a PR exists for a given repository and branch we could easily fetch the PR and update it's title and body. Adding the good-first-issue tag |
Thanks! |
Hi Sir @gounthar May I work on this ? |
Hello @biru-codeastromer, You're welcome to do so, thanks for your help. 👍 |
Thanks Sir , will be raising a PR soon ! |
Hi Sir, I wanted to tell you in the original setup and building process itself of the repo using maven , I am getting error in build without even making changes . |
Probably related to your environment https://ci.jenkins.io/job/Tools/job/plugin-modernizer-tool/job/main/522/pipeline-graph/ |
What is your environment (OS, Java version and vendor, Maven version)? |
Hi Sir, Thank you for your response. Here are the details of my environment: Operating System: macOS Sequoia (Version 15.3 Beta) |
Hello Sir this is what I am facing after running
|
I suspect the issue might be related to SpotBugs compatibility with Java 23. Could you confirm if Java 23 is supported, or if there are additional configurations I should check? |
The jenkins project only support LTS version of Java (11, 17, 21 etc..) and 25 (end of the year). There is no guarantee it works by using other Java version |
Okay Sir , then I will try with 21 Version of java and update you here if I get successful . Thanks for your help ! |
Hi Sir, I switched to Java 21 as per your suggestion, and the project built successfully 🎉. Thank you very much for your guidance!
|
That's very good news, thanks for the feedback! 👍 |
Hi Sir , I wanted to bring to your attention some pre-existing test failures in the plugin-modernizer-tool project while running |
Details of the Failures: -Test Name: upgradeNextMajorParentVersionTestWithBaseline Other Similar Failures: -upgradeNextMajorParentVersionTestWithBom I verified that these failures are not related to my changes, as they persist even when reverting my modifications. Steps I Took: |
|
Do you think Sir I should raise the PR then without addressing the pre-existing test failures? These failures are not related to my changes, and if these test checks are not required for timing, I can proceed with the PR as is. |
Possibly related to #708 Your PR need to be rebased when merged on main. This was cause by bom update (https://github.com/jenkinsci/bom/releases) and removal from 2.452.x line) and some tests still using hardcoded value |
Thanks Sir for the confirmation . Okay I will proceed accordingly. |
|
I am again getting errors in |
ci.jenkins.io is green. Double check your configuration |
Okay Sir ! |
What feature do you want to see added?
We've been running update campaigns for a while now, and some plugin maintainers have already reviewed and accepted our automatic PRs. However, some haven't reviewed or merged them, which was expected since the plugins we are targeting aren't as closely monitored as the most installed ones.
Whenever we relaunch a campaign on the same set of plugins, we force-push the same code, but it seems we don't modify the PR title and body. Between the campaigns, the text for the title and/or body may have changed because the project is evolving, and new JTE templates are being regularly updated.
Furthermore, some plugin maintainers gave some feedback (one of them being pretty harsh) about the PR body, so the PR body will evolve in order to satisfy most of the plugin maintainers.
That's why I propose that we consider changing the PR title and body when relaunching a campaign, provided the title and body haven't been edited since the PR was created.
Upstream changes
No response
Are you interested in contributing this feature?
No response
The text was updated successfully, but these errors were encountered: