search

mkobit / jenkins-pipeline-shared-library-example

Basic template example of a Jenkins Pipelines Shared Library that is tested using https://github.com/mkobit/jenkins-pipeline-shared-libraries-gradle-plugin
MIT License
70 stars 34 forks source link

Add a Groovy build.gradle example #5

Open mkobit opened 6 years ago

mkobit commented 6 years ago

@kleini commented on Thu Mar 15 2018

I would to stay at first with Groovy DSL in build.gradle files. Can you provide an example how to use your plugin in a build.gradle file?

@mkobit commented on Thu Mar 15 2018

I think this issue is better suited for https://github.com/mkobit/jenkins-pipeline-shared-library-example - is it alright if I migrate it there?

@mkobit commented on Thu Mar 15 2018

A few notes that may be helpful

@kleini commented on Thu Mar 15 2018

You're right. Migrate it. Thanks for your hints. I will try to get it working for me and then contribute to your examples.

@kleini commented on Thu Mar 15 2018

I already got it working. Why did my first try to reference your plugin from my build.gradle file fail? No idea. I thought it was because it was written in Kotlin. The fault sits always in front of the computer!

mkobit commented 6 years ago

I already got it working. Why did my first try to reference your plugin from my build.gradle file fail?

One possibility is the Gradle version, as the latest release requires Gradle 4.6. Hard to say without a build scan/stacktrace.

I'll leave this issue open for now.

Note, it may be useful to have examples of both a Groovy or Kotlin build script.

kleini commented 6 years ago

In my case Gradle was version 4.6 and gradle tasks just showed as if the build.gradle file is completely empty. It did not notice the plugin section and the referenced plugin at all. And not error message. Hard to say, what may have caused this.