[JIRA] [statusmonitor] (JENKINS-21793) Status Monitor Plugin not rendering HTML properly
Jared Griffith created JENKINS-21793 Status Monitor Plugin not rendering HTML properly Issue Type: Bug Affects Versions: current Assignee: danielgalan Attachments: status_monitor.png Components: statusmonitor Created: 12/Feb/14 11:12 PM Description: Status Monitor Plugin not rendering HTML properly Environment: CentOS 6.x, Oracle JDK 1.7.0_40, Jenkins 1.550-1.1 Project: Jenkins Labels: plugin Priority: Major Reporter: Jared Griffith 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] [crowd2] (JENKINS-21184) SSO Appears to be Broken
Jared Griffith commented on JENKINS-21184 SSO Appears to be Broken Oh man, I guess I didn't have the SSO check box clicked. Nevermind, it's working fine now. My bad. 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] [crowd2] (JENKINS-21184) SSO Appears to be Broken
Jared Griffith resolved JENKINS-21184 as Fixed SSO Appears to be Broken See my comment. id10t error. Change By: Jared Griffith (10/Jan/14 9:38 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 -- 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] [crowd2] (JENKINS-21184) SSO Appears to be Broken
Jared Griffith commented on JENKINS-21184 SSO Appears to be Broken I don't see a .property file in that directory, or any file that has property in it's name. 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] [crowd2] (JENKINS-21184) SSO Appears to be Broken
Jared Griffith commented on JENKINS-21184 SSO Appears to be Broken It's 1.6. I haven't seen anything in the logs unfortunately. 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] [crowd2] (JENKINS-21184) SSO Appears to be Broken
Jared Griffith commented on JENKINS-21184 SSO Appears to be Broken Here's the only thing in the logs: Jan 05, 2014 9:36:57 AM de.theit.jenkins.crowd.CrowdConfigurationService init INFO: Groups given for Crowd configuration service: tech Jan 05, 2014 9:36:57 AM com.atlassian.crowd.service.client.ClientPropertiesImpl loadAndLogPropertyString INFO: Loading property: 'application.name' : 'jenkins' Jan 05, 2014 9:36:57 AM com.atlassian.crowd.service.client.ClientPropertiesImpl loadAndLogPropertyString INFO: Loading property: 'application.login.url' : 'http://crowd.picsauditing.com:8095/crowd/console/' Jan 05, 2014 9:36:57 AM com.atlassian.crowd.service.client.ClientPropertiesImpl loadAndLogPropertyString INFO: Loading property: 'session.tokenkey' : 'session.tokenkey' Jan 05, 2014 9:36:57 AM com.atlassian.crowd.service.client.ClientPropertiesImpl loadAndLogPropertyString INFO: Loading property: 'session.lastvalidation' : 'session.lastvalidation' Jan 05, 2014 9:36:57 AM com.atlassian.crowd.service.client.ClientPropertiesImpl loadAndLogPropertyString INFO: Loading property: 'session.validationinterval' : '2' Jan 05, 2014 9:36:57 AM com.atlassian.crowd.service.client.ClientPropertiesImpl loadAndLogPropertyString INFO: Failed to find value for property: cookie.domain Also, I don't know if I had upgraded the Crowd2 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 -- 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] [sauce-ondemand] (JENKINS-17303) Null Pointer Exception for hasSauceOnDemandResults in jobs that aren't using that plugin
Jared Griffith commented on JENKINS-17303 Null Pointer Exception for hasSauceOnDemandResults in jobs that arent using that plugin Yeah, upgrading to the latest plug in corrects the problem. Thanks. 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-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Jared Griffith commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ Yeah, never mind, it looks like there was some funkiness with the connection to the git repo. I just upgraded it and everything is working just fine. 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-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Jared Griffith commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ I'm not sure if this should be re-opened or not, but the same error is back in 1.508. 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-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Jared Griffith commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ Once I saw the error, I downgraded back to 1.507 Jenkins and still had the same git client plugin, which resolved the issue. 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-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Jared Griffith commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ It's the same error that is above and I was seeing with the 1.3.0 git plugin and 1.0.4 git client plugin. Git was working just fine prior to that as I and a couple of other co-workers had committed changes to our main repo. I can upgrade it again and see if I see the same behavior since we are outside of work hours at this time. I'll let you know in like 15 minutes. 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-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Jared Griffith commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ Works perfectly with the 1.0.5 version. Thank you! 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-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Jared Griffith commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ Love Nyberg - The quick fix that worked for me is detailed by Mikhail Andreev. Though I would add: Stop Jenkins Go to your Jenkins Plugin directory - JENKINS_HOME/plugins. Remove the git.* and git-client.* Download: http://mirrors.karan.org/jenkins/plugins/git/1.2.0/ http://mirrors.karan.org/jenkins/plugins/git-client/1.0.3/ Copy *.hpi to JENKINS_HOME/plugins and Downgrade to these plugins. Start Jenkins. Works fine at that point. 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-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Jared Griffith commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ I'm having the same problems and saw similar problems with Atlassian's Stash and Fisheye when they moved to jgit. There was some horrible / stupid hacks that I had to do to get it to work. I would vote not using jgit as this was working properly before. For as long as I have used Jenkins + Git (+5 years), I have never experienced a problem with the old implementation. If you are seeing memory / output problems, it's probably not from Git. 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-17303) Null Pointer Exception for hasSauceOnDemandResults in jobs that aren't using that plugin
Jared Griffith created JENKINS-17303 Null Pointer Exception for hasSauceOnDemandResults in jobs that arent using that plugin Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: sauce-ondemand Created: 20/Mar/13 9:39 PM Description: When browsing to any job, I am seeing the following in the jenkins.log, even when the job is not using the plugin. WARNING: Caught exception evaluating: from.hasSauceOnDemandResults() in /job/OrgFullTest_AlphaIE/. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.plugins.sauce_ondemand.SauceOnDemandProjectAction.hasSauceOnDemandResults(SauceOnDemandProjectAction.java:39) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsBoolean(ExpressionSupport.java:71) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:97) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] (JENKINS-15044) Tomcat deployment Fails when using Deploy To Container plugin
Jared Griffith commented on JENKINS-15044 Tomcat deployment Fails when using Deploy To Container plugin Thanks! 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-14949) Deploy several wars/ears to several servers
Jared Griffith commented on JENKINS-14949 Deploy several wars/ears to several servers It would be awesome to see the functionality that the Bamboo Tomcat Deploy plug in has built into this plug in for Jenkins. Though, it's essentially giving the ability to add multiple "deploy ear/war to container" items in one job. 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-15044) Tomcat deployment Fails when using Deploy To Container plugin
Jared Griffith commented on JENKINS-15044 Tomcat deployment Fails when using Deploy To Container plugin I think the initial configuration was set with the manager in the URL. I changed it and it's working now. Now, will there ever be the ability to deploy to multiple containers from within the same job (like Bamboo currently has)? P.S. I am a much bigger fan of your application, and am trying to remove Bamboo completely from our application building process for various reasons. 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-15044) Tomcat deployment Fails when using Deploy To Container plugin
Jared Griffith created JENKINS-15044 Tomcat deployment Fails when using Deploy To Container plugin Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: deploy Created: 04/Sep/12 11:49 PM Description: When using the deploy to container plugin to deploy to a Tomcat 7 container, I get the following error: Deploying /var/lib/jenkins/jobs/Demo1/workspace/target/ROOT.war to container Tomcat 7.x Remote ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to exception org.codehaus.cargo.container.ContainerException: Failed to redeploy /var/lib/jenkins/jobs/Demo1/workspace/target/ROOT.war at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:195) at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:64) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:90) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:77) at hudson.FilePath.act(FilePath.java:842) at hudson.FilePath.act(FilePath.java:824) at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:77) at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:47) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1527) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.io.FileNotFoundException: http://demo1-vm.picsauditing.com:8080/manager//manager/text/list at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1434) at org.codehaus.cargo.container.tomcat.internal.TomcatManager.invoke(TomcatManager.java:504) at org.codehaus.cargo.container.tomcat.internal.TomcatManager.list(TomcatManager.java:622) at org.codehaus.cargo.container.tomcat.internal.TomcatManager.getStatus(TomcatManager.java:635) at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:176) ... 16 more java.io.FileNotFoundException: http://demo1-vm.picsauditing.com:8080/manager//manager/text/list at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1434) at org.codehaus.cargo.container.tomcat.internal.TomcatManager.invoke(TomcatManager.java:504) at org.codehaus.cargo.container.tomcat.internal.TomcatManager.list(TomcatManager.java:622) at org.codehaus.cargo.container.tomcat.internal.TomcatManager.getStatus(TomcatManager.java:635) at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:176) at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:64) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:90) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:77) at hudson.FilePath.act(FilePath.java:842) at hudson.FilePath.act(FilePath.java:824) at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:77) at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:47) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1527)
[JIRA] (JENKINS-14025) HipChat / Jenkins Plugin not notifying rooms
Jared Griffith resolved JENKINS-14025 as Not A Defect HipChat / Jenkins Plugin not notifying rooms False alarm Change By: Jared Griffith (25/Jun/12 2:25 PM) Status: Open Resolved Resolution: NotADefect 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-14025) HipChat / Jenkins Plugin not notifying rooms
Jared Griffith commented on JENKINS-14025 HipChat / Jenkins Plugin not notifying rooms Yeah, false alarm. I got it working correctly. 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-13807) Email-ext Plugin Does Not work
Jared Griffith created JENKINS-13807: Summary: Email-ext Plugin Does Not work Key: JENKINS-13807 URL: https://issues.jenkins-ci.org/browse/JENKINS-13807 Project: Jenkins Issue Type: Bug Components: email-ext Affects Versions: current Environment: CentOS 6.2, Sun JDK 6.0.31, Jenkins ver. 1.464 installed from yum repo Reporter: Jared Griffith I have installed and tried to activate the email-ext plugin, but when I try to enable the extension for a particular job, it does not work. I am getting the following error with the Firefox Javascript debugger: Timestamp: 05/16/2012 06:16:42 PM Error: emailExtInit is not defined Source File: http://jenkins.picsauditing.com/static/5f664cc9/scripts/hudson-behavior.js Line: 480 Please help. The latest version of the plug in is installed and was installed from the Jenkins Plugin UI. -- 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
