Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-48812

Developer guide for gradle-jpi-plugin

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Minor Minor
    • gradle-jpi-plugin
    • None

      Could we have a 'developer guide' for anyone wishing to develop the gradle-jpi-plugin?

      I'm not sure how you can publish it to a local maven repo and then use it in an actual plugin

          [JENKINS-48812] Developer guide for gradle-jpi-plugin

          Jeremy Marshall created issue -
          Daniel Spilker made changes -
          Assignee Original: Daniel Spilker [ daspilker ] New: Steve Hill [ sghill ]

          Steve Hill added a comment -

          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 - 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 made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Steve Hill added a comment -

          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.

          Steve Hill added a comment - 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.
          Steve Hill made changes -
          Resolution New: Won't Do [ 10001 ]
          Status Original: In Progress [ 3 ] New: Closed [ 6 ]

            sghill Steve Hill
            jeremym Jeremy Marshall
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: