Steve Hill added a comment - 2019-04-17 15:36 Hi jeremym , We're using the standard maven-publish gradle plugin for this. Running the publishToMavenLocal task will publish the project locally. To consume your locally-published plugin, it'd just be a matter of adding a buildscript dependency and the mavenLocal() repository. buildscript { repositories { mavenLocal() } dependencies { classpath 'org.jenkins-ci.tools:gradle-jpi-plugin:<version>' } } Composite builds are also a great option if you're looking to iterate quickly without publishing. Does this help? I'm happy to link out to gradle's guides for development, but hesitant to introduce a full developer guide. We're trying to leverage the standard tooling as much as possible so we can rely on gradle's docs - which are much more likely to be kept up-to-date than our own. I recognize this issue was opened quite a long time ago and may no longer be relevant. I'll mark it as resolved if I don't hear back in a week or so.

Steve Hill added a comment - 2019-06-26 16:11 Trying to move this plugin in a direction of leveraging standard gradle features and encouraging gradle's official docs over creating a developer guide that is likely to get out of date very quickly for this plugin.