[JIRA] (JENKINS-42497) Local Signature XYZ does not match with external Signature ABC

2017-03-06 Thread patterson....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ben patterson commented on  JENKINS-42497  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Local Signature XYZ does not match with external Signature ABC   
 

  
 
 
 
 

 
 Ankur Bansal could you provide a stack trace?  And when you say "Once I update the shared secret"...what exactly do you do in that case? Do you come up with a new secret?   Also, could you please point out what version of Jenkins you are using? Thank you.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-26811) Pull Request Builder integration

2017-01-13 Thread patterson....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ben patterson resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This already happens in the current version. Closing.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-26811  
 
 
  Pull Request Builder integration   
 

  
 
 
 
 

 
Change By: 
 ben patterson  
 
 
Status: 
 Open 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-41058) Not able to retrieve ghprbActualCommitAuthor when commited from Github UI

2017-01-13 Thread patterson....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ben patterson commented on  JENKINS-41058  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not able to retrieve ghprbActualCommitAuthor when commited from Github UI   
 

  
 
 
 
 

 
 asrar parveen could you elaborate please? Why do you need this, how are you attempting to get it, what have you tried?  
 

  
 
 
 
 

 
 
 

 
 
 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-38828) Add pull request builder support for tracking credential usage

2016-10-09 Thread patterson....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ben patterson commented on  JENKINS-38828  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add pull request builder support for tracking credential usage   
 

  
 
 
 
 

 
 Also see here: https://github.com/jenkinsci/ghprb-plugin/issues/428  
 

  
 
 
 
 

 
 
 

 
 
 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] [shelve-project-plugin] (JENKINS-8063) Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384

2014-04-18 Thread patterson....@gmail.com (JIRA)














































ben patterson
 commented on  JENKINS-8063


Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384















Hi - Thanks for the ping. 

I cut the release this morning. v1.5 should be available for use within the next day.



























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] [shelve-project-plugin] (JENKINS-8063) Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384

2014-04-18 Thread patterson....@gmail.com (JIRA)















































ben patterson
 resolved  JENKINS-8063 as Fixed


Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384
















Change By:


ben patterson
(18/Apr/14 12:53 PM)




Status:


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


[JIRA] [shelve-project-plugin] (JENKINS-10544) shelve project button missing on some projects

2014-04-18 Thread patterson....@gmail.com (JIRA)















































ben patterson
 resolved  JENKINS-10544 as Fixed


shelve project button missing on some projects
















Fixed in release v 1.5





Change By:


ben patterson
(18/Apr/14 1:07 PM)




Status:


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


[JIRA] [shelve-project-plugin] (JENKINS-11374) Add deletion option on list of Shelved Projects

2014-04-18 Thread patterson....@gmail.com (JIRA)















































ben patterson
 resolved  JENKINS-11374 as Fixed


Add deletion option on list of Shelved Projects
















Available in v 1.5 of plugin





Change By:


ben patterson
(18/Apr/14 1:08 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/d/optout.


[JIRA] [shelve-project-plugin] (JENKINS-10544) shelve project button missing on some projects

2014-03-21 Thread patterson....@gmail.com (JIRA)














































ben patterson
 started work on  JENKINS-10544


shelve project button missing on some projects
















Change By:


ben patterson
(21/Mar/14 9:51 AM)




Status:


Open
InProgress



























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] [shelve-project-plugin] (JENKINS-10544) shelve project button missing on some projects

2014-03-21 Thread patterson....@gmail.com (JIRA)














































ben patterson
 commented on  JENKINS-10544


shelve project button missing on some projects















maselvaraj's pull request corrects this problem. It'll be included in the next rev of this 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/d/optout.


[JIRA] [shelve-project-plugin] (JENKINS-17299) ShelvedProject plugin seems to cause config-ping-pong, i.e. addition and removal of the same content in the xml-config files of jobs

2014-03-21 Thread patterson....@gmail.com (JIRA)















































ben patterson
 resolved  JENKINS-17299 as Duplicate


ShelvedProject plugin seems to cause config-ping-pong, i.e. addition and removal of the same content in the xml-config files of jobs
















Change By:


ben patterson
(21/Mar/14 9:58 AM)




Status:


Open
Resolved





Resolution:


Duplicate



























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] [shelve-project-plugin] (JENKINS-20987) Shelve-Project Plugin - The shelved projects still appear under ALL view

2014-03-21 Thread patterson....@gmail.com (JIRA)















































ben patterson
 resolved  JENKINS-20987 as Cannot Reproduce


Shelve-Project Plugin - The shelved projects still appear under ALL view
















the job config is being fixed in jenkins-10544 for the job config. 





Change By:


ben patterson
(21/Mar/14 10:00 AM)




Status:


Open
Resolved





Resolution:


CannotReproduce



























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] [shelve-project-plugin] (JENKINS-8063) Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384

2014-02-28 Thread patterson....@gmail.com (JIRA)















































ben patterson
 assigned  JENKINS-8063 to ben patterson



Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384
















Change By:


ben patterson
(01/Mar/14 1:18 AM)




Assignee:


ashlux
benpatterson



























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] [shelve-project-plugin] (JENKINS-8063) Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384

2014-02-28 Thread patterson....@gmail.com (JIRA)














































ben patterson
 started work on  JENKINS-8063


Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384
















Change By:


ben patterson
(01/Mar/14 1:18 AM)




Status:


Reopened
InProgress



























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] [shelve-project-plugin] (JENKINS-8063) Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384

2014-02-28 Thread patterson....@gmail.com (JIRA)














































ben patterson
 commented on  JENKINS-8063


Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384















Fix checked in; will close at next release.



























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] [shelve-project-plugin] (JENKINS-9169) Exception after shelving the project

2014-02-28 Thread patterson....@gmail.com (JIRA)















































ben patterson
 resolved  JENKINS-9169 as Cannot Reproduce


Exception after shelving the project
















Unable to reproduce. Stacktrace looks like it's from a Jenkins snapshot version. Closing this issue for now.





Change By:


ben patterson
(01/Mar/14 1:22 AM)




Status:


Open
Resolved





Resolution:


CannotReproduce



























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] [shelve-project-plugin] (JENKINS-9169) Exception after shelving the project

2014-02-28 Thread patterson....@gmail.com (JIRA)















































ben patterson
 closed  JENKINS-9169 as Cannot Reproduce


Exception after shelving the project
















Change By:


ben patterson
(01/Mar/14 1:22 AM)




Status:


Resolved
Closed



























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] [shelve-project-plugin] (JENKINS-20987) Shelve-Project Plugin - The shelved projects still appear under ALL view

2014-02-28 Thread patterson....@gmail.com (JIRA)














































ben patterson
 commented on  JENKINS-20987


Shelve-Project Plugin - The shelved projects still appear under ALL view















This issue should go away with a page refresh. Otherwise I'm unable to reproduce 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







-- 
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] [shelve-project-plugin] (JENKINS-11023) Add Wipe out workspace option

2013-07-30 Thread patterson....@gmail.com (JIRA)















































ben patterson
 resolved  JENKINS-11023 as Fixed


Add Wipe out workspace option
















Fixed/released in v 1.4.4.

Now, in the process of shelving, a workspace will be wiped out before the project is zipped.





Change By:


ben patterson
(30/Jul/13 12:05 PM)




Status:


InProgress
Resolved





Fix Version/s:


current





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] [shelve-project-plugin] (JENKINS-11023) Add Wipe out workspace option

2013-07-30 Thread patterson....@gmail.com (JIRA)














































ben patterson
 commented on  JENKINS-11023


Add Wipe out workspace option















Brian - I did not look at the HTTP GET option, but the workspace wipeout happens within the context of the shelving itself, so I would expect this to solve your problem as well. If it does not, please open another ticket for that particular flavor.



























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] [shelve-project-plugin] (JENKINS-11023) Add Wipe out workspace option

2013-07-30 Thread patterson....@gmail.com (JIRA)















































ben patterson
 closed  JENKINS-11023 as Fixed


Add Wipe out workspace option
















Release 1.4.4





Change By:


ben patterson
(30/Jul/13 12:07 PM)




Status:


Resolved
Closed



























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] [shelve-project-plugin] (JENKINS-11023) Add Wipe out workspace option

2013-07-29 Thread patterson....@gmail.com (JIRA)















































ben patterson
 assigned  JENKINS-11023 to ben patterson



Add Wipe out workspace option
















Change By:


ben patterson
(29/Jul/13 1:22 PM)




Assignee:


ashlux
benpatterson



























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] [shelve-project-plugin] (JENKINS-11023) Add Wipe out workspace option

2013-06-05 Thread patterson....@gmail.com (JIRA)














































ben patterson
 started work on  JENKINS-11023


Add Wipe out workspace option
















Change By:


ben patterson
(06/Jun/13 1:18 AM)




Status:


Open
InProgress



























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] [shelve-project-plugin] (JENKINS-11023) Add Wipe out workspace option

2013-06-05 Thread patterson....@gmail.com (JIRA)















































ben patterson
 assigned  JENKINS-11023 to ashlux



Add Wipe out workspace option
















Pull request #2





Change By:


ben patterson
(06/Jun/13 1:26 AM)




Assignee:


benpatterson
ashlux



























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] [core] (JENKINS-17927) hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem

2013-05-14 Thread patterson....@gmail.com (JIRA)















































ben patterson
 closed  JENKINS-17927 as Duplicate


hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem
















Similar issue to Jenkins-16446. Resolved here by killing and re-adding a custom view. It may have been failing on the regular _expression_ (which had worked before--I did not change it when I upgraded jenkins), but this time I used the 'job filter' option, rather than the usual regex on the custom view and that solved the problem.

I'm closign this as a likely duplicate though.





Change By:


ben patterson
(14/May/13 12:09 PM)




Status:


Open
Closed





Resolution:


Duplicate



























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] [core] (JENKINS-17927) hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem

2013-05-11 Thread patterson....@gmail.com (JIRA)














































ben patterson
 commented on  JENKINS-17927


hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem















I forgot to mention an important detail: this only happens for unauthenticated users. Once I log in, this goes away. It's the home screen though, so it doesn't present to product folks very well.



























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] [core] (JENKINS-17927) hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem

2013-05-11 Thread patterson....@gmail.com (JIRA)














































ben patterson
 updated  JENKINS-17927


hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem
















Change By:


ben patterson
(11/May/13 11:43 AM)




Description:


UpgradedtolatestJenkinsfrom1.489.Wehaveanumberofpluginsincludingmaven-plugininstalled.Forunauthenticatedusers,wegetanhttp500errorwithinthedefaultview.IwouldattempttodisabletheMavenplugintoseeifIcangetridoftheerror,butitisconsideredpartofMavencore.
[Edit:Alsoworthnoting:thisonlyoccursforunauthenticatedusers.Onceloggedin,itgoesaway.Itsthehomescreenthough,soeveryoneseesit.FWIW,occursondifferentbrowsers,too.]
PartialStacktracehere.Attachingscreenshotandmoreofthestacktrace.Exception:org.apache.commons.jelly.JellyTagException:jar:file:/usr/local/jboss-4.2.3.GA/server/production/tmp/deploy/tmp2463229018850549093hudson-exp.war/WEB-INF/lib/jenkins-core-1.514.jar!/hudson/model/View/index.jelly:44:43:st:includeorg.apache.commons.jelly.JellyTagException:jar:file:/usr/local/jboss-4.2.3.GA/server/production/tmp/deploy/tmp2463229018850549093hudson-exp.war/WEB-INF/lib/jenkins-core-1.514.jar!/lib/hudson/projectView.jelly:63:22:d:invokeBodyhudson.maven.MavenModulecannotbecasttohudson.model.TopLevelItemStacktrace:javax.servlet.ServletException:org.apache.commons.jelly.JellyTagException:jar:file:/usr/local/jboss-4.2.3.GA/server/production/tmp/deploy/tmp2463229018850549093hudson-exp.war/WEB-INF/lib/jenkins-core-1.514.jar!/hudson/model/View/index.jelly:44:43:st:includeorg.apache.commons.jelly.JellyTagException:jar:file:/usr/local/jboss-4.2.3.GA/server/production/tmp/deploy/tmp2463229018850549093hudson-exp.war/WEB-INF/lib/jenkins-core-1.514.jar!/lib/hudson/projectView.jelly:63:22:d:invokeBodyhudson.maven.MavenModulecannotbecasttohudson.model.TopLevelItem	atorg.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117)	atorg.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)	atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666)	atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:770)	atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:736)	atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:770)	atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:583)	atorg.kohsuke.stapler.Stapler.service(Stapler.java:214)	atjavax.servlet.http.HttpServlet.service(HttpServlet.java:803)	atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)	atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)	athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)	athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)	atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)	atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)	athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)	atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)	atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)	athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atorg.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)	atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)snip



























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 

[JIRA] [core] (JENKINS-17927) hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem

2013-05-10 Thread patterson....@gmail.com (JIRA)














































ben patterson
 created  JENKINS-17927


hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


jenkinshttp500.png, morestacktrace.txt



Components:


core, maven2



Created:


11/May/13 3:04 AM



Description:


Upgraded to latest Jenkins from 1.489. We have a number of plugins including maven-plugin installed. For unauthenticated users, we get an http500 error within the default view. 

I would attempt to disable the Maven plugin to see if I can get rid of the error, but it is considered part of Maven core.

Partial Stacktrace here. Attaching screenshot and more of the stacktrace.

Exception: org.apache.commons.jelly.JellyTagException: jar:file:/usr/local/jboss-4.2.3.GA/server/production/tmp/deploy/tmp2463229018850549093hudson-exp.war/WEB-INF/lib/jenkins-core-1.514.jar!/hudson/model/View/index.jelly:44:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/usr/local/jboss-4.2.3.GA/server/production/tmp/deploy/tmp2463229018850549093hudson-exp.war/WEB-INF/lib/jenkins-core-1.514.jar!/lib/hudson/projectView.jelly:63:22: d:invokeBody hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem
Stacktrace: 
javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/usr/local/jboss-4.2.3.GA/server/production/tmp/deploy/tmp2463229018850549093hudson-exp.war/WEB-INF/lib/jenkins-core-1.514.jar!/hudson/model/View/index.jelly:44:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/usr/local/jboss-4.2.3.GA/server/production/tmp/deploy/tmp2463229018850549093hudson-exp.war/WEB-INF/lib/jenkins-core-1.514.jar!/lib/hudson/projectView.jelly:63:22: d:invokeBody hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem
	at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117)
	at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:736)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:214)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	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 org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124)
	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)

snip