[JIRA] (JENKINS-13468) Would like to create/use a central "catalog" . . .

2012-11-07 Thread d...@fortysix.ch (JIRA)















































domi
 resolved  JENKINS-13468 as Fixed


Would like to create/use a central "catalog" . . .
















implemented in 2.5





Change By:


domi
(07/Nov/12 8:34 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-13468) Would like to create/use a central "catalog" . . .

2012-09-22 Thread d...@fortysix.ch (JIRA)














































domi
 commented on  JENKINS-13468


Would like to create/use a central "catalog" . . .















I was thinking about these two feature requests (JENKINS-13468 JENKINS-15276) and I think we can combine these with the new git-server plugin functionality kohsuke just introduced: https://wiki.jenkins-ci.org/display/JENKINS/Git+Server+Plugin



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-13468) Would like to create/use a central "catalog" . . .

2012-05-23 Thread fmer...@qualcomm.com (JIRA)

[ 
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




[JIRA] (JENKINS-13468) Would like to create/use a central "catalog" . . .

2012-04-17 Thread d...@fortysix.ch (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161694#comment-161694
 ] 

domi commented on JENKINS-13468:


That sounds like a good idea and actually the current implementation does 
already allow you to do something in the same direction...

The directory at '/scriptler/scripts' gets synchronized at every 
startup of Jenkins and automatically imports every *.groovy file. I agree, this 
is not perfect yet, but It might help you to get started.
Based on that functionality I could think of a second (userdefined) directory 
where you could just dump new scripts and we could add some 
functionality/button to trigger the sync - instead of having to restart Jenkins.
I'll think about it a bit more, but I'm sure we can do something useful here...

> 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




[JIRA] (JENKINS-13468) Would like to create/use a central "catalog" . . .

2012-04-16 Thread fmer...@qualcomm.com (JIRA)
Frank Merrow created JENKINS-13468:
--

 Summary: 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