-
Notifications
You must be signed in to change notification settings - Fork 22
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
Implemented a small version for issue#688 #702
Conversation
Hello sir, Just wanted your input regarding these changes, would like to work on this further. |
Changing it there is risky, as we might use the same keyword in different situations. I prefer to define a property in Thanks! |
What if we use a comment to match the version? "#recommanded version managed by updatecli"? But I think a maven property with filtering on the resource looks more clean |
Hello sir, As per your suggestion i'm trying to use maven filtering on the recipes.yml to dynamically update the version but filtering isn't working as expected, Please share any info on why this is so. |
@@ -19,4 +19,5 @@ private RecipesConsts() { | |||
public static final String OLD_BOM_VERSION_PATTERN = | |||
""; // Old release line like 2.150.x, no need to filter by pattern | |||
public static final String INCREMENTAL_REPO_ID = "incrementals"; | |||
public static final String JENKINS_CORE_VERSION = "${jenkins.core.minimum.version}"; |
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.
Why not Settings.getJenkinsMinimumVersion()
instead of filtering java source?
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.
Sorry sir, I missed it.
updating now.
Thank you.
@@ -148,7 +148,7 @@ recipeList: | |||
artifactId: plugin | |||
newVersion: 5.X | |||
- io.jenkins.tools.pluginmodernizer.core.recipes.UpgradeJenkinsVersion: | |||
minimumVersion: 2.479.1 | |||
minimumVersion: "${jenkins.core.minimum.version}" |
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.
This is not the minimum version. This value should not be changed since it's the first LTS supporting Java 17 and required for parent 5.x upgrade.
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.
Only value https://github.com/jenkins-infra/plugin-modernizer-tool/pull/685/files must be filtered/changed
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.
In the example that sir gave i.e #685 this was also modified so i was testing with this.
Now i understand the issue.
Thanks.
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.
Only 2.452.4 was incremented to 2.462.3. The rest of value must not be changed
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.
Yes sir, I misunderstood previously
Now i understand my mistake
Thank you.
@@ -442,7 +442,7 @@ recipeList: | |||
artifactId: plugin | |||
newVersion: 4.51 # See https://www.jenkins.io/blog/2022/12/14/require-java-11/ | |||
- io.jenkins.tools.pluginmodernizer.core.recipes.UpgradeJenkinsVersion: | |||
minimumVersion: 2.346.3 |
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.
This is NOT the minimum version. It's the last LTS supporting Java 8. This value will never changes
plugin-modernizer-core/pom.xml
Outdated
<directory>src/main/resources/META-INF/rewrite</directory> | ||
<includes> | ||
<include>recipes.yml</include> | ||
</includes> | ||
</resource> | ||
<resource> |
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.
To be removed
I do not know if you don't share details |
@@ -416,7 +416,7 @@ recipeList: | |||
- io.jenkins.tools.pluginmodernizer.UpgradeParentVersion | |||
- io.jenkins.tools.pluginmodernizer.AddPluginsBom | |||
- io.jenkins.tools.pluginmodernizer.core.recipes.UpgradeJenkinsVersion: | |||
minimumVersion: 2.462.3 | |||
minimumVersion: "${jenkins.core.minimum.version}" |
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.
I don't see it in the pom
Hello sir, in versions.properties - openrewrite.maven.plugin.version = ${openrewrite.maven.plugin.version} is causing circular refernce error so i replaced it with a constant for now, How to modify it properly without any breaking changes. |
Is this change okay? |
Tests are failing |
@@ -1,4 +1,4 @@ | |||
openrewrite.maven.plugin.version = ${openrewrite.maven.plugin.version} | |||
openrewrite.maven.plugin.version = 5.10.0 |
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.
This is not correct. We need to continue filtering from the pom
@@ -227,6 +227,26 @@ | |||
</resources> | |||
<plugins> | |||
|
|||
<plugin> |
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.
What is the reason to override the properties-maven-plugin rather than adding a new ?
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.
But i did add a unique execution id so, won't it run concurrently instead of overriding?
Hello sir, The tests are failing on linux |
Hello sir, Some errors seems to be introduced recently, tests are failing in "UpgradeJenkinsVersionTest", could you please take a look at that. |
Superseded by #776 |
updated updatecli.d/jenkins-lts.yaml to update the jenkins recommended version
Testing done
Added 2 more targets in the updatecli.d/jenkins-lts.yaml to update the jenkins versions in recipes.yml
With the further input from the maintainers would like to work on it further.
Submitter checklist