-
Notifications
You must be signed in to change notification settings - Fork 9
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
Check Jenkinsfile presence #43
Check Jenkinsfile presence #43
Conversation
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.
Thank you, Sridhar.
I have a small suggestion: it would be helpful if we could keep the pull requests (PRs) "atomic", focusing on one goal at a time.
For instance, you removed a dependency in the pom file. While this is a valuable change, it could have been submitted as a separate PR later.
This approach helps us maintain a clearer history and makes reviews more straightforward.
Reverted back unrelated changes from the PR. Thanks @gounthar. |
Thanks a lot! 🙏 |
Fixes #43 Implement the remediation function for `MAVEN_REPOSITORIES_HTTP` to replace 'http' with 'https' in repository URLs. * Modify `plugin-modernizer-core/src/main/java/io/jenkins/tools/pluginmodernizer/core/model/PreconditionError.java` to include the remediation function that uses `PomModifier` to replace 'http' with 'https' in repository URLs. * Add a method `replaceHttpWithHttps` in `plugin-modernizer-core/src/main/java/io/jenkins/tools/pluginmodernizer/core/utils/PomModifier.java` to replace 'http' with 'https' in repository URLs. * Add tests in `plugin-modernizer-core/src/test/java/io/jenkins/tools/pluginmodernizer/core/extractor/MetadataCollectorTest.java` to verify the functionality of the remediation function for `MAVEN_REPOSITORIES_HTTP`. --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/gounthar/plugin-modernizer-tool/issues/43?shareId=XXXX-XXXX-XXXX-XXXX).
related to #41
Updates...
Now we are able to check the presence of Jenkinsfile in a plugin directory. Right now, the execution of this recipe stores the metadata locally in the target directory in JSON format. As suggested by @gounthar in this comment we can store the result in external sources in the following PR after discussions.
Testing done
Submitter checklist