[JIRA] [hipchat-plugin] (JENKINS-33214) Hipchat plugin not working with authenticating proxy

2016-02-29 Thread mich...@glauche.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Glauche created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33214 
 
 
 
  Hipchat plugin not working with authenticating proxy  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 hipchat-plugin 
 
 
 

Created:
 

 29/Feb/16 12:24 PM 
 
 
 

Environment:
 

 V. 1.0.0 tested 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Michael Glauche 
 
 
 
 
 
 
 
 
 
 
Hipchat plugin does read the proxy configuration from the jenkins settings, but seems to ignore the authentication part, when I click the "test" button I'm getting a 407 proxy authentication error. 
Looking at the source, i also don't see any authentication passed to the HttpClient. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 

[JIRA] [core] (JENKINS-22685) Jenkins cannot restart Windows service

2014-08-21 Thread mich...@glauche.de (JIRA)














































Michael Glauche
 commented on  JENKINS-22685


Jenkins cannot restart Windows service















Having the same problem with 1.565.1, running as windows service. Also stuck at "Please wait while Jenkins is restarting ..."



























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/d/optout.


[JIRA] [maven] (JENKINS-22486) API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception.

2014-06-05 Thread mich...@glauche.de (JIRA)














































Michael Glauche
 commented on  JENKINS-22486


API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception. 















Additionally, with the maven plugin 2.2 and older maven (3.2.1) jobs will deadlock if you use the -T option:

"pool-1-thread-1 for channel" - Thread t@19
   java.lang.Thread.State: WAITING
	at sun.misc.Unsafe.park(Native Method)

	parking to wait for 1efa1efa (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
	at java.util.concurrent.locks.LockSupport.park(LockSupport.java:173)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1937)
	at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:370)
	at java.util.concurrent.ExecutorCompletionService.take(ExecutorCompletionService.java:176)
	at org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder.multiThreadedProjectTaskSegmentBuild(LifecycleThreadedBuilder.java:111)
	at org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder.build(LifecycleThreadedBuilder.java:73)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:147)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
	at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:117)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:600)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
	at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:178)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:600)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:134)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:69)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:328)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:315)
	at java.util.concurrent.FutureTask.run(FutureTask.java:150)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:898)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:920)
	at java.lang.Thread.run(Thread.java:736)



   Locked ownable synchronizers:

	locked 29272927 (a java.util.concurrent.locks.ReentrantLock$NonfairSync)






























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/d/optout.


[JIRA] [git] (JENKINS-19994) Unable to delete workspace

2013-11-26 Thread mich...@glauche.de (JIRA)














































Michael Glauche
 commented on  JENKINS-19994


Unable to delete workspace















Same problem here, with windows 2008 r2 server, git plugin 2.0 with JGit implementation. 



























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-17117) git Diff is not displayed correctly with rodecode

2013-03-07 Thread mich...@glauche.de (JIRA)














































Michael Glauche
 created  JENKINS-17117


git Diff is not displayed correctly with rodecode 















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


git



Created:


07/Mar/13 11:56 AM



Description:


When using rhodecode as git repository browser the diff link seems wrong. Example: 
http://rhodecode.server.com/Test/diff/gitA/pom.xml?diff2=0a04d700929e404dacaae7eff7e69389156d1b98diff1=0a04d700929e404dacaae7eff7e69389156d1b98diff=diff+to+revision

(Note the hashes are the same for the last and current version, thus no changes will be displayed in rhodecode)

The other links work fine, so i don't suspect the rhodecode installation is wrong.




Project:


Jenkins



Priority:


Major



Reporter:


Michael Glauche

























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-15367) Jenkins kicks off the wrong downstream builds for Maven

2012-11-03 Thread mich...@glauche.de (JIRA)














































Michael Glauche
 commented on  JENKINS-15367


Jenkins kicks off the wrong downstream builds for Maven















Hi,
I did try out your fork, and it seems to work fine for my scenarios. (i.e. direct snapshot dependencies got triggered, other versions didn't)



























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-12735) No upstream or downstream resolution with Maven version ranges

2012-11-01 Thread mich...@glauche.de (JIRA)














































Michael Glauche
 commented on  JENKINS-12735


No upstream or downstream resolution with Maven version ranges















This could be the reason, I remember there was some breaking change from 3.0.3 to 3.0.4 with SNAPSHOTS in version ranges, but i can't find it anymore.

But, there's still MNG-3092 , which could be the main reason behind it. This thread on the maven list also goes in detail about the problem.



























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-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs

2012-10-30 Thread mich...@glauche.de (JIRA)














































Michael Glauche
 commented on  JENKINS-15652


All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs















I'm having exactly the same issue with 1.487 



























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-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs

2012-10-30 Thread mich...@glauche.de (JIRA)












































 
Michael Glauche
 edited a comment on  JENKINS-15652


All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
















I'm having exactly the same issue with 1.487 
(running jenkins with jdk 1.6.0_27-b07, on 64bit Windows)



























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-12735) No upstream or downstream resolution with Maven version ranges

2012-10-27 Thread mich...@glauche.de (JIRA)














































Michael Glauche
 updated  JENKINS-12735


No upstream or downstream resolution with Maven version ranges
















Change By:


Michael Glauche
(27/Oct/12 11:05 AM)




Attachment:


JENKINS-12735.zip



























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-12735) No upstream or downstream resolution with Maven version ranges

2012-10-27 Thread mich...@glauche.de (JIRA)














































Michael Glauche
 commented on  JENKINS-12735


No upstream or downstream resolution with Maven version ranges















I did attach two simple test-scenarios, both with project "A" and "B".

In the "working" scenario, jenkins did see the relationship correctly between B and A, so that when B was build A will be build later. (makes sense, direct dependency did change)

In the "failing" scenario, the "B" project did create a release (0.0.1), move the development version to 0.0.2-SNAPSHOT. However the A project decides that they want only the latest stable version, so they switch their dependency to the 0.0.1 release.

Now, however, when Jenkins (1.487) builds B with 0.0.2-SNAPSHOT it does trigger the A job too! (which makes no sense, because A is using the "stable" build 0.0.1, which should not change, so no re-building ins needed.)
This did lead to a massive increase of number of projects building (and me having to switch off the option on 100+ jenkins jobs ..)

I think the behavior was correct at least in 1.474, where only depdencencies with exactly the same dependency version got build.



























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-12735) No upstream or downstream resolution with Maven version ranges

2012-10-26 Thread mich...@glauche.de (JIRA)














































Michael Glauche
 commented on  JENKINS-12735


No upstream or downstream resolution with Maven version ranges















I'm having the same problem as Jay, this change makes this option useless, as we would end up having nearly every project depended on other project. 
Please re-open it.



























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-12735) No upstream or downstream resolution with Maven version ranges

2012-10-26 Thread mich...@glauche.de (JIRA)














































Michael Glauche
 reopened  JENKINS-12735


No upstream or downstream resolution with Maven version ranges
















Please look on this again, the latest change create huge list of downstream projects to build. (although they are not really affected)





Change By:


Michael Glauche
(26/Oct/12 9:11 AM)




Resolution:


Fixed





Status:


Resolved
Reopened



























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-13781) NPE in UserRelevanceView when no user is logged on

2012-05-25 Thread mich...@glauche.de (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163187#comment-163187
 ] 

Michael Glauche commented on JENKINS-13781:
---

There's still a NPE in line 77, method public boolean matchesRun(Run run)

User user = getUser();
+   if (user == null) {
+   return false;
+   }



 NPE in UserRelevanceView when no user is logged on
 --

 Key: JENKINS-13781
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13781
 Project: Jenkins
  Issue Type: Bug
  Components: view-job-filters
Reporter: Michael Glauche
Assignee: Jacob Robertson
Priority: Blocker

 I'm getting a NPE when i try to use the view-job-filters plugin with a recent 
 Jenkins install (did try with 1463,1464):
 /.jenkins/war/WEB-INF/lib/jenkins-core-1.464.jar!/lib/hudson/projectView.jelly:60:22:
  d:invokeBody java.lang.NullPointerException
 at 
 org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:716)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:282)
 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:270)
 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 
 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:270)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 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.kohsuke.stapler.jelly.CompressTag.doTag(CompressTag.java:44)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
 at 
 org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
 at 
 org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)
 at 
 org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53)
 at 
 org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:107)
 ... 53 more
 Caused by: java.lang.RuntimeException: 
 org.apache.commons.jelly.JellyTagException: 
 jar:file://.jenkins/war/WEB-INF/lib/jenkins-core-1.464.jar!/lib/hudson/projectView.jelly:60:22:
  d:invokeBody java.lang.NullPointerException
 at 
 org.kohsuke.stapler.jelly.groovy.JellyBuilder.doInvokeMethod(JellyBuilder.java:287)
 at 
 org.kohsuke.stapler.jelly.groovy.Namespace$ProxyImpl.invoke(Namespace.java:92)
 at $Proxy25.projectView(Unknown Source)
 at lib.JenkinsTagLib$projectView.call(Unknown Source)
 at hudson.model.View.main.run(main.groovy:14)
 at 
 org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:66)
 at 
 org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:59)
 at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146)
 at 

[JIRA] (JENKINS-13781) NPE in UserRelevanceView when no user is logged on

2012-05-25 Thread mich...@glauche.de (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163187#comment-163187
 ] 

Michael Glauche edited comment on JENKINS-13781 at 5/25/12 9:06 AM:


There's still a NPE in line 77, method public boolean matchesRun(Run run)

{code:title=matchesRun|borderStyle=solid}
User user = getUser();
+   if (user == null) {
+   return false;
+   }
{code} 


  was (Author: mglauche):
There's still a NPE in line 77, method public boolean matchesRun(Run 
run)

User user = getUser();
+   if (user == null) {
+   return false;
+   }


  
 NPE in UserRelevanceView when no user is logged on
 --

 Key: JENKINS-13781
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13781
 Project: Jenkins
  Issue Type: Bug
  Components: view-job-filters
Reporter: Michael Glauche
Assignee: Jacob Robertson
Priority: Blocker

 I'm getting a NPE when i try to use the view-job-filters plugin with a recent 
 Jenkins install (did try with 1463,1464):
 /.jenkins/war/WEB-INF/lib/jenkins-core-1.464.jar!/lib/hudson/projectView.jelly:60:22:
  d:invokeBody java.lang.NullPointerException
 at 
 org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:716)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:282)
 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:270)
 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 
 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:270)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 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.kohsuke.stapler.jelly.CompressTag.doTag(CompressTag.java:44)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
 at 
 org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
 at 
 org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)
 at 
 org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53)
 at 
 org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:107)
 ... 53 more
 Caused by: java.lang.RuntimeException: 
 org.apache.commons.jelly.JellyTagException: 
 jar:file://.jenkins/war/WEB-INF/lib/jenkins-core-1.464.jar!/lib/hudson/projectView.jelly:60:22:
  d:invokeBody java.lang.NullPointerException
 at 
 org.kohsuke.stapler.jelly.groovy.JellyBuilder.doInvokeMethod(JellyBuilder.java:287)
 at 
 org.kohsuke.stapler.jelly.groovy.Namespace$ProxyImpl.invoke(Namespace.java:92)
 at $Proxy25.projectView(Unknown Source)
 at lib.JenkinsTagLib$projectView.call(Unknown Source)
 

[JIRA] (JENKINS-13781) NPE in UserRelevanceView when no user is logged on

2012-05-25 Thread mich...@glauche.de (JIRA)

 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Glauche reopened JENKINS-13781:
---


 NPE in UserRelevanceView when no user is logged on
 --

 Key: JENKINS-13781
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13781
 Project: Jenkins
  Issue Type: Bug
  Components: view-job-filters
Reporter: Michael Glauche
Assignee: Jacob Robertson
Priority: Blocker

 I'm getting a NPE when i try to use the view-job-filters plugin with a recent 
 Jenkins install (did try with 1463,1464):
 /.jenkins/war/WEB-INF/lib/jenkins-core-1.464.jar!/lib/hudson/projectView.jelly:60:22:
  d:invokeBody java.lang.NullPointerException
 at 
 org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:716)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:282)
 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:270)
 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 
 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:270)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 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.kohsuke.stapler.jelly.CompressTag.doTag(CompressTag.java:44)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
 at 
 org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
 at 
 org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)
 at 
 org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53)
 at 
 org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:107)
 ... 53 more
 Caused by: java.lang.RuntimeException: 
 org.apache.commons.jelly.JellyTagException: 
 jar:file://.jenkins/war/WEB-INF/lib/jenkins-core-1.464.jar!/lib/hudson/projectView.jelly:60:22:
  d:invokeBody java.lang.NullPointerException
 at 
 org.kohsuke.stapler.jelly.groovy.JellyBuilder.doInvokeMethod(JellyBuilder.java:287)
 at 
 org.kohsuke.stapler.jelly.groovy.Namespace$ProxyImpl.invoke(Namespace.java:92)
 at $Proxy25.projectView(Unknown Source)
 at lib.JenkinsTagLib$projectView.call(Unknown Source)
 at hudson.model.View.main.run(main.groovy:14)
 at 
 org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:66)
 at 
 org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:59)
 at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
 ... 84 more
 Caused by: org.apache.commons.jelly.JellyTagException: 
 jar:file://.jenkins/war/WEB-INF/lib/jenkins-core-1.464.jar!/lib/hudson/projectView.jelly:60:22:
  d:invokeBody java.lang.NullPointerException
 at