[JIRA] (JENKINS-39414) Cannot edit Job Configuration anymore after installing version 2.28
Title: Message Title Mike Caspar commented on JENKINS-39414 Re: Cannot edit Job Configuration anymore after installing version 2.28 Oleg Nenashev. I wanted to confirm for you that I have the ruby-runtime in a similar environment to Noah above and the same problem. I fixed by rolling back to 2.27 in the meantime. Thanks Oleg for finding this. 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-37771) "Run the build in a RVM-managed environment" field gets unchecked after restarting the Jenkins server.
Title: Message Title Mike Caspar commented on JENKINS-37771 Re: "Run the build in a RVM-managed environment" field gets unchecked after restarting the Jenkins server. I don't know if it helps or hinders, but this Seems to be related (or similar) to this old issue... https://issues.jenkins-ci.org/browse/JENKINS-38145 Hope it helps. 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-36246) docker build step error with descriptorImpl on jenkins startup
Title: Message Title Mike Caspar commented on JENKINS-36246 Re: docker build step error with descriptorImpl on jenkins startup After posting, saw the message about 5 similar issues. Appears to be a duplicate of JENKINS-25692 ? Perhaps this has more detail .. If not.. sorry about the duplicate. 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-36246) docker build step error with descriptorImpl on jenkins startup
Title: Message Title Mike Caspar created an issue Jenkins / JENKINS-36246 docker build step error with descriptorImpl on jenkins startup Issue Type: Bug Assignee: vjuranek Components: docker-build-step-plugin Created: 2016/Jun/27 2:36 PM Environment: ubuntu 14.04 jenkins 2.x (I believe it was there when I had v1 but am not sure) Labels: plugin exception Priority: Minor Reporter: Mike Caspar I have been getting this set of errors on jenkins boot for a while (not sure exactly how long).. I thnk I had it with v1 but am not sure. If this is in the wrong project, please move on my behalf. Here's a stack trace... Jun 27, 2016 10:25:38 AM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error WARNING: Failed to instantiate Key[type=org.jenkinsci.plugins.dockerbuildstep.DockerBuilder$DescriptorImpl, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Error injecting constructor, java.util.ServiceConfigurationError: com.github.dockerjava.api.command.DockerCmdExecFactory: Provider com.github.dockerjava.jaxrs.DockerCmdExecFactoryImpl not a subtype at org.jenkinsci.plugins.dockerbuildstep.DockerBuilder$DescriptorImpl.(DockerBuilder.java:95) 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at
[JIRA] (JENKINS-35505) Modify Plugin to work in Pipeline
Title: Message Title Mike Caspar updated an issue Jenkins / JENKINS-35505 Modify Plugin to work in Pipeline Change By: Mike Caspar Priority: Minor Major 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-36099) Request to use alternate Queue Name regression failed
Title: Message Title Mike Caspar closed an issue as Fixed Jenkins / JENKINS-36099 Request to use alternate Queue Name regression failed Change By: Mike Caspar 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-36099) Request to use alternate Queue Name regression failed
Title: Message Title Mike Caspar resolved as Fixed Jenkins / JENKINS-36099 Request to use alternate Queue Name regression failed Change By: Mike Caspar Status: In Progress Resolved Resolution: Fixed 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-36099) Request to use alternate Queue Name regression failed
Title: Message Title Mike Caspar commented on JENKINS-36099 Re: Request to use alternate Queue Name regression failed 1.0.16 will have fix (v2.10 jenkins minimum) 1.0.17 will have fix (1.x version) 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-36099) Request to use alternate Queue Name regression failed
Title: Message Title Mike Caspar commented on JENKINS-36099 Re: Request to use alternate Queue Name regression failed Fixed in 1.0.15 generateMessageSettings was not including QueueName when setting MessageSettings. 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-36099) Request to use alternate Queue Name regression failed
Title: Message Title Mike Caspar created an issue Jenkins / JENKINS-36099 Request to use alternate Queue Name regression failed Issue Type: Bug Assignee: Mike Caspar Components: ironmq-notifier-plugin Created: 2016/Jun/20 11:29 PM Priority: Minor Reporter: Mike Caspar When overriding the default QueueName, it was not used in all cases. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36099) Request to use alternate Queue Name regression failed
Title: Message Title Mike Caspar started work on JENKINS-36099 Change By: Mike Caspar Status: Open In Progress 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-35505) Modify Plugin to work in Pipeline
Title: Message Title Mike Caspar updated an issue Jenkins / JENKINS-35505 Modify Plugin to work in Pipeline Change By: Mike Caspar Priority: Major Minor 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-35505) Modify Plugin to work in Pipeline
Title: Message Title Mike Caspar updated an issue Jenkins / JENKINS-35505 Modify Plugin to work in Pipeline Change By: Mike Caspar Priority: Minor Major 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-35505) Modify Plugin to work in Pipeline
Title: Message Title Mike Caspar started work on JENKINS-35505 Change By: Mike Caspar Status: Open In Progress 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] [ironmq-notifier-plugin] (JENKINS-35505) Modify Plugin to work in Pipeline
Title: Message Title Mike Caspar created an issue Jenkins / JENKINS-35505 Modify Plugin to work in Pipeline Issue Type: Improvement Assignee: Mike Caspar Components: ironmq-notifier-plugin Created: 2016/Jun/09 3:39 PM Labels: plugin Priority: Minor Reporter: Mike Caspar Start making modifications to allow execution from within a Pipeline script. Add Comment
[JIRA] [core] (JENKINS-31089) Signature verification failed in update site 'default'
Title: Message Title Mike Caspar commented on JENKINS-31089 Re: Signature verification failed in update site 'default' Hi there, For me, I find that if I just ignore the error, I can see the new modules (updates) by just going back to the root url. I personally don't feel comfortable going in and forcing a lower encryption level when a key rey-gen could apparently fix this.. This will complicate java upgrades, docker containers of jenkins servers, potentially puppet and chef builds of servers, etc. More importantly, I don't see that there will be an easy way to know when to "unhack" the setting, leaving the lower level of key setting potentially forever. I can't imagine going in and playing with the setting after every Jenkins version upgrade. It's awesome for those that need workarounds right now, but please remember, you'll need a way to remember to set it back some day in the future. Maybe it's no big deal, but I think I'm being responsible to ask this question at least once? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-20077) WARNING: Could not find dependency cloudbees-credentials of bees-sdk-plugin
Title: Message Title Mike Caspar closed an issue as Duplicate Closed based on comment from Daniel Beck about being resolved in a different issue. Re-open if needed Jenkins / JENKINS-20077 WARNING: Could not find dependency cloudbees-credentials of bees-sdk-plugin Change By: Mike Caspar Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31089) Signature verification failed in update site 'default'
Title: Message Title Mike Caspar commented on JENKINS-31089 Re: Signature verification failed in update site 'default' Hi there, I saw no change so I thought.. OK.. maybe it's caching of some sort. Let's restart my server. Much better progress. The initial signature error is gone and doesn't show any exceptions in the logs. That first message has gone away to now be replaced by a new one (1.634,java 1.8.0_66-b17, ubuntu 14.04). Strangely, there is no error in the jenkins.log. I get the following in the jenkins.log Oct 24, 2015 9:32:43 AM hudson.model.UpdateSite updateData INFO: Obtained the latest update center data file for UpdateSource default followed by the following in the web interface... at /pluginManager/checkUpdatesServer Signature verification failed in downloadable 'hudson.tasks.Maven.MavenInstaller' (show details) Would you like me to open a ticket somewhere or just consider this message to be sufficient ? (which module if so). Not sure.. same (related) problem or different one? Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31089) Signature verification failed in update site 'default'
Title: Message Title Mike Caspar edited a comment on JENKINS-31089 Re: Signature verification failed in update site 'default' Hi there,I saw no change so I thought.. OK.. maybe it's caching of some sort. Let's restart my server. Much better progress. The initial signature error is gone and doesn't show any exceptions in the logs for the original problem . . However, That first message has gone away to now be replaced by a new one (1.634,java 1.8.0_66-b17, ubuntu 14.04).Strangely, there is no *error* in the jenkins.log. I get the following in the jenkins.logOct 24, 2015 9:32:43 AM hudson.model.UpdateSite updateDataINFO: Obtained the latest update center data file for UpdateSource defaultfollowed by the following in the web interface...at /pluginManager/checkUpdatesServer*Signature verification failed in downloadable 'hudson.tasks.Maven.MavenInstaller' (show details)*Would you like me to open a ticket somewhere or just consider this message to be sufficient ? (which module if so). Not sure.. same (related) problem or different one?Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ruby-runtime-plugin] (JENKINS-30898) Ruby Runtime Plugin - org.jruby.util.collections.WeakHashSet not found
Title: Message Title Mike Caspar commented on JENKINS-30898 Re: Ruby Runtime Plugin - org.jruby.util.collections.WeakHashSet not found I have the same problem starting today. I noticed that this happens on 1.633 but when downgrading to 1.632 this error goes away. (Hope that helps). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ruby-runtime-plugin] (JENKINS-30898) Ruby Runtime Plugin - org.jruby.util.collections.WeakHashSet not found
Title: Message Title Mike Caspar edited a comment on JENKINS-30898 Re: Ruby Runtime Plugin - org.jruby.util.collections.WeakHashSet not found I have the same problem starting today. The plugin was previously loaded. I noticed that this happens on 1.633 but when downgrading to 1.632 this error goes away.(Hope that helps). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-29518) 1.621 available, but 1.620 is most recent listed in changelog
Title: Message Title Mike Caspar commented on JENKINS-29518 Re: 1.621 available, but 1.620 is most recent listed in changelog Hi there, Having a similar problem with sudo apt-get update Thought I'd mention it here instead of opening another issue as it seems related. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [nodejs-plugin] (JENKINS-28093) Plugin Manager gets exception because of FileNotFound nodejs Installer
Mike Caspar created JENKINS-28093 Plugin Manager gets exception because of FileNotFound nodejs Installer Issue Type: Bug Assignee: Unassigned Components: nodejs-plugin Created: 25/Apr/15 12:18 AM Description: When selecting the Check Now option in Plugin Manager (Update Manager), a stack trace appears There seems to be two separate issues. 1 - The NodeJS file not found. 2 - The exception is not caught and handled. I don't know which module the update manager is located, sorry.. .if it's more appropriate to move it there, then please go ahead.. Things seem to start here... Caused by: java.io.FileNotFoundException: http://mirrors.jenkins-ci.org/updates/updates/jenkins.plugins.nodejs.tools.NodeJSInstaller.json.html?id=jenkins.plugins.nodejs.tools.NodeJSInstallerversion=1.610 WARNING: Error while serving http://servernameHidden:8080/pluginManager/checkUpdatesServer java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46) at org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:183) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [chromedriver] (JENKINS-12765) ChromeDriver won't install on slave
Mike Caspar commented on JENKINS-12765 ChromeDriver wont install on slave I just tried this plugin for the first time on 1.541 I get a "similar" but not the same error. I didn't want to creat a new Jira as it seems it may be similar. Actions taken were... -install plugin -restart server -during server startup, the following occurs... Installing chromedriver to /var/lib/jenkins/tools/chromedriver ERROR: Failed to install chromedriver ha:(long string removed for clarity)=java.io.IOException: No installation data is downloaded from chromedriver yet at org.jenkinsci.plugins.chromedriver.DownloadableImpl.select(DownloadableImpl.java:74) at org.jenkinsci.plugins.chromedriver.DownloadableImpl.resolve(DownloadableImpl.java:35) at org.jenkinsci.plugins.chromedriver.ComputerListenerImpl.process(ComputerListenerImpl.java:43) at org.jenkinsci.plugins.chromedriver.ComputerListenerImpl.onOnline(ComputerListenerImpl.java:29) at jenkins.model.Jenkins.init(Jenkins.java:849) at hudson.model.Hudson.init(Hudson.java:82) at hudson.model.Hudson.init(Hudson.java:78) at hudson.WebAppMain$3.run(WebAppMain.java:222) 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 -- 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/groups/opt_out.
[JIRA] (JENKINS-17343) Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available
Mike Caspar commented on JENKINS-17343 Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available Hi there. I upgraded from 1.506 to 1.508 and started having this problem. It was easily solved by downgrading to 1.506. This may allow you to keep working while looking for resolution. 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 -- 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/groups/opt_out.
[JIRA] (JENKINS-14476) Option to set gravatar to only check for new gravatar every x minutes to cut down on requests from jenkins server to gravatar.com
Mike Caspar created JENKINS-14476 Option to set gravatar to only check for new gravatar every x minutes to cut down on requests from jenkins server to gravatar.com Issue Type: Improvement Assignee: redsolo Components: gravatar Created: 18/Jul/12 2:55 AM Description: I love the Gravatar plug-in. I'm wondering if there's any possibility of having it only check for a new gravatar every "x" minutes to keep bandwidth utilization down. Thanks Project: Jenkins Labels: plugin Priority: Minor Reporter: Mike Caspar 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-13530) JENKINS_HOME ignored on Bundled Windows EXE.
Mike Caspar created JENKINS-13530: - Summary: JENKINS_HOME ignored on Bundled Windows EXE. Key: JENKINS-13530 URL: https://issues.jenkins-ci.org/browse/JENKINS-13530 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: Windows XP. Reporter: Mike Caspar I've been having trouble with the JENKINS_HOME and think I've figured out a way around the problem, but at the same time, would like to report a problem with the BUNDLED download. At FIRST, I thought I was doing something wrong, but have confirmed the problem does NOT exist in the WAR that I install into my Tomcat 7 server. If I load the SETUP.EXE, when the SERVICE starts up, it simply IGNORED my System Environment variables completely. Nothing I do changes this. If I stop the service and download the WAR and load it into Tomcat it PROPERLY reads the Environment Variable and locates the appropriate folder. Again, the problem is only with the windows Service Installer from the Windows Setup. I have even set HUDSON_HOME (just in case). Thanks (wasn't sure if CORE was the right place to put this). -- 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
