Gradle / Jenkins JAR发布到GitHub

Question

I am working on a bunch of projects which are all part of a larger project (pipeline) and thus need to be tested together quite often. Manual tests are not as great as they should be, so I decided to run things in the future using Gradle + Jenkins CI. My first tests were successfuly, unit tests etc are running great and Jenkins builds my JAR files that I want to deploy quite nicely.

Since all my projects are open source and available on GitHub, I'd love to set things up to be published on the GitHub releases page of the respective (sub-) project, eg something like this:

• I develop, commit with a Git tag
• Jenkins sees this via a Hook, runs the Gradle Script to build things and upon successful tests publishes the JAR file created in my project to a new release version on GitHub

Unfortunately, this is not working quite as expected, eg using the Plugin here , which for example only pushed the packaged source code and not the JAR file. Otherwise this works well and I might just have overseen something?

Does someone have experience on this ?

Answer 1

I think you are mistaking what a Github release is. From a Github point of view, a release is not some folder where you would deploy your arfifact (eg your built Jar) but is basically just a Git tag that points to a certain commit and says "ok, I consider this commit d215465454 to be my release 1.2.3". It is just a pointer to a commit so you can always find the Git history for any specific "release". Please see Git excellent Tagging documentation for more information.

Moreover, you probably shouldn't need to expose the actual jar to your end users. Instead you could rely on Bintray or Artifactory to deploy your actual jar artifact and your end users could configure their gradle build file to depend on your jar.