jenkins-pipeline-shared-library-example
jenkins-pipeline-shared-library-example copied to clipboard
mkobit
Add a Groovy build.gradle example
@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
- https://github.com/mkobit/jenkins-pipeline-shared-libraries-gradle-plugin/tree/01762ba70b05b950dff251dcd99811ed1895bdb0/src/pipelineTestResources/projects has all of the different types of samples that the test suite runs against. Some of those may help for what you are looking for
- https://github.com/mkobit/jenkins-pipeline-shared-libraries-gradle-plugin/blob/01762ba70b05b950dff251dcd99811ed1895bdb0/src/pipelineTestResources/projects/gradle-configuration-groovy/build.gradle is a close approximation of how to configure the
build.gradle, but I can add a more specific setup to the other repository
@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!
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.
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.
