[JIRA] (JENKINS-38740) Add support for loading system scripts from job dsl
Title: Message Title Daniel Spilker closed an issue as Won't Do Jenkins / JENKINS-38740 Add support for loading system scripts from job dsl Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38740) Add support for loading system scripts from job dsl
Title: Message Title Daniel Spilker resolved as Won't Do You can use any Java library in Job DSL scripts. And you can package common Job DSL code in a library so that it can be used in any location. See https://github.com/jenkinsci/job-dsl-plugin/wiki/User-Power-Moves#using-libraries for details. The Job DSL Gradle example shows how to setup a build system and tests for Job DSL code. You can use that as a starting point: https://github.com/sheehan/job-dsl-gradle-example Jenkins / JENKINS-38740 Add support for loading system scripts from job dsl Change By: Daniel Spilker Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38740) Add support for loading system scripts from job dsl
Title: Message Title Kevin Phillips created an issue Jenkins / JENKINS-38740 Add support for loading system scripts from job dsl Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2016/Oct/05 2:42 PM Priority: Major Reporter: Kevin Phillips As one goes about adding Groovy DSL to generate jobs for a production development site you realize that there are many jobs which share similar DSL code. Currently you are able to share this code by extracting the common stuff out into a separate groovy file and import it into each of your worker scripts. However, there is one small - albeit very significant - limitation here: the common groovy scripts must exist in the local workspace where the job DSL is being run. What I would like to see is some way of making common DSL scripts available from the Jenkins master so any job running under it can import them. What I'm thinking is something like what the Scriptler plugin does, where you can store common script in the global configuration (ie: on the Jenkins master) and import / reference them in your groovy build steps (so long as you run them as 'system scripts' on the master anyway). Add Comment
