According to Steve, some manifest entries are truly needed to be there and he asked to have your opinion as well on this.

This is also correct. Without a license or dependency information, the update center won't even accept the plugin publishing. You can lurk around in https://github.com/search?q=repo%3Ajenkins-infra%2Fupdate-center2%20Manifest&type=code for the implementation. My advice would be injecting all fields for now

Actually, I am facing one more issue with the CI recently. All my (approx.) 20 integration tests, work correctly on my local env. But when these run within the CI, all of them are failing. Upon investigation, the issue is with something like 'Kotlin Incremental Classpath Snapshot Diff' Upon lookup, it was the issue in Kotlin 1.9x, it was fixed with disabling the kotlin.incremental flag, but in my case it didn't fix the issue. Also, tried cleaning the Test project tempdir after each test, try some other hacky ways, but it didn't get solve Kindly look into the latest build logs on the main branch or presently open PR PS: Using Kotlin 2.2, Gradle 9RC3, Java 17

Hi @Oleg Nenashev, I have raised an issue regarding Gradle 9.0 on Gradle GitHub repo. Kindly look into it! Thanks 🙂

Hello @Oleg Nenashev, @sghill, @rahulsom ! 👋 Proceeding with PCT, I was brainstorming about how we should integrate it in our convention plugin.... Till now I have two ways, 1. We can somehow make Gradle, output a pom.xml from the consumer project and then we can feed that to the PCT CLI 2. The other way can be, getting to the root of PCT and then adding a functionality for Gradle Script 'updation' as it does for Maven by replacing the particular versions of 'jenkins-core', and other transitive deps. The second method is very brittle in my opinion, as Maven has a particular structure while Gradle scripts are more of a freestyle n dynamic.... I wanted to have everybody's opinion on this. PS: I have injected the missing Manifest entries, and now they match with Maven's HPI

FWIW I have to miss today's meeting due to some personal agenda while at the conference, sorry

Hello @Oleg Nenashev, @sghill, @rahulsom 👋 Need your guidance/ideas on this. https://github.com/aaravmahajanofficial/plugin-compat-tester/commit/88f7732a0236f00912406d73d7ab5b7bca2b5d4a#commitcomment-163731089

Hello @Oleg Nenashev, @sghill, @rahulsom I have managed to make PCT find the Generated POM file & make use of that; generated via

./gradlew generatePomFileForMavenJpiPublication

first and then ran PCT. I got the

Build Successful

message as per the logs. I am facing another issue with the

Hooks

, internal PCT logic etc. IMO the problem arises as internal logic expects Maven in the project. How to go about this? Here is the latest code and build logs: https://github.com/aaravmahajanofficial/plugin-compat-tester/commit/d9435db6f54cea85dddb724dfd7758df6c50af8b

Hi @Oleg Nenashev, @sghill @rahulsom 👋 Want your review on my current progress for PCT. I think we are almost done with Native Gradle Support, though some minor tweaks are expected. Branch: https://github.com/aaravmahajanofficial/plugin-compat-tester/tree/feat/add-native-gradle-support-to-pct I have tested with some plugins which use JPI plugin presently, the gradle is getting detected by PCT properly and the build is successful. You can test the same with this command:

java -jar .\target\plugins-compat-tester-cli.jar test-plugins --war .\target\jenkins-war-2.522.war --local-checkout-dir ${insert-gradle-plugin-repo} --working-dir "$(pwd)/pct-work"

After this, we can raise an official PR to Jenkins PCT official repo. PS: Regarding the PCT hooks issue, I have disabled 4 hooks, JenkinsTestHarness(1 and 2) Servelet, HPIPlugin. https://github.com/jenkinsci/plugin-compat-tester/compare/master...aaravmahajanoff[…]cial:plugin-compat-tester:feat/add-native-gradle-support-to-pct https://github.com/jenkinsci/plugin-compat-tester/compare/master...aaravmahajanoff[…]cial:plugin-compat-tester:feat/add-native-gradle-support-to-pct

Hello @Oleg Nenashev, I have posted a new blog at the official Dev Gradle Community Page. Added a follow up comment also, to ref it in August Newsletter. Thanks 🙂 --- https://dev.to/gradle-community/gradle-convention-plugin-for-developing-jenkins-plugins-4n1d https://github.com/gradle/community/issues/228#issuecomment-3196170196

@Aarav Mahajan I will try to join tonight, but I am at the meetup. Worst case, will follow up asynchronously. Let me know if my participation is a must. And yes, please note that my blog post comments are suggestions, it already looks fine

@Aarav Mahajan This is for jenkins plugins, but there'll be some overlap.

Hello @Oleg Nenashev, @rahulsom, @sghill 🙂 As we discussed, I have initiated an announcement/discussion, regarding the convention plugin on the Jenkins Dev. Mailing List https://groups.google.com/g/jenkinsci-dev/c/4kN2opnRLtg

Revised Jenkins Dev. Mailing list announcement. Thanks! :)

@Aarav Mahajan just in case, where do we stand with the blog draft? Do you consider it finished? Of course, there is also an open question about hosting and, potentially, https://www.jenkins.io/blog/

I will try to adopt the convention plugin in https://github.com/jenkinsci/gradle-plugin - it would allow to compare Maven and updated Gradle flows in the same repository. @Alexis @Alexey Venderov @wolfs - any objections?

Hi @Oleg Nenashev 🙂 I have updated the blog. Handpicked few parts from the Dev. Mailing list post. https://dev.to/gradle-community/gradle-convention-plugin-for-developing-jenkins-plugins-4n1d Kindly have a look....

Do I need to wait for the common *credentials (*that we discussed about), before I submit a request for getting my plugin hosted at jenkins community repo?

@sghill @rahulsom FYI https://groups.google.com/g/jenkinsci-dev/c/AXZyPqgQzos

@Aarav Mahajan to confirm, it looks like we will be able to publish the demo on the Jenkins YouTube channel

Hi @Oleg Nenashev, opened up the New Hosting Request. Kindly have a look. https://github.com/jenkins-infra/repository-permissions-updater/issues/4608

Hi @Oleg Nenashev, @rahulsom, @sghill 👋 I have submitted a new PR for the new blog post at official Jenkins Blog https://github.com/jenkins-infra/jenkins.io/pull/8391

@Aarav Mahajan I would also suggest posting a brief status update on https://groups.google.com/g/jenkinsci-dev/c/00r_hESYtKY (hosting request, renaming of groupdIds if you do that, de.to blog, pending jenkins.io blog)

@Oleg Nenashev I have done the updations to my project page. Thanks! https://github.com/gradle/community/pull/254

@Oleg Nenashev what do you think about this? https://github.com/jenkins-infra/repository-permissions-updater/issues/4608#issuecomment-3242009873

Thanks @Oleg Nenashev for helping with the repo transfer process 🙂 Is this message expected, when I go to repo settings? IIRC I was able to access the settings in the fork one by jenkins-bot....

@Aarav Mahajan my apologies, I forgot about https://github.com/wiremock/gradle-wiremock-extension-plugins/pull/26 and merging it. Does it have any relation to GSoC per se?

@Aarav Mahajan do we meet today? I definitely think we could do a retro next week, but I am not sure about the meeting today

Congrats with https://www.jenkins.io/blog/2025/08/31/aarav-mahajan-gsoc-gradle-convention-plugin-for-jenkins-plugin-development/ !

@Aarav Mahajan For the "late" changes that were finished after the submission date (e.g. hosting, Jenkins blog, etc.), You can still reference them on https://community.gradle.org/events/gsoc/2025/jenkins-plugins-toolchain/ , e.g. in a separate section for post-project updates.