[
https://issues.jenkins-ci.org/browse/JENKINS-13468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163136#comment-163136
]
Frank Merrow commented on JENKINS-13468:
----------------------------------------
This issue finally bubbled up back into view . . .
I've tried it and the "scripts" directory will do nicely, thank you . . . on a
couple of our Jenkins, Jenkins got installed in C:\Program File (x86) which
causes some access issues if the user is not running CMD.EXE as Admin . . . but
other than that minor annoyance, this solution is very usable for my situation.
THANK YOU.
Frank
> Would like to create/use a central "catalog" . . .
> --------------------------------------------------
>
> Key: JENKINS-13468
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13468
> Project: Jenkins
> Issue Type: New Feature
> Components: scriptler
> Environment: Windows . . .
> Reporter: Frank Merrow
> Assignee: domi
>
> We have a large and growing number of Jenkins instances . . . We don't have
> many Groovy script, but rather than carrying them around by hand, it would be
> nice to be able to put them in once place (network share for instance) and
> access them from any Jenkins.
> Note this isn't exactly like your public repositories, because I don't want
> to have to import them . . . while certain scripts might be local to a given
> Jenkins, for the global Jenkins script . . . if they are changed in one
> Jenkins, I would like that update to appear for all Jenkins attached to the
> repository.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
