[JIRA] (JENKINS-15848) CVS plugin, add support for 'C' parameter
Aykut SAY commented on JENKINS-15848 CVS plugin, add support for C parameter I am using Jenkins ver. 1.480.2 and cvs plugin 2.7 but this issue is still exist. I checked the config.jelly and there is no forceCleanCopy entry. Also there is no "help-forceCleanCopy.html" file. 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-7364) Sauce OnDemand video/server log logic doesn't work with Twist
evernat resolved JENKINS-7364 as Incomplete Sauce OnDemand video/server log logic doesnt work with Twist No response from the reporter on this old issue, so resolving as incomplete. Reopen if needed. Change By: evernat (22/Jan/13 8:43 AM) Status: Open Resolved Resolution: Incomplete 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-15440) Emailing users at the end of a failed build very slow for big Jenkins instance using subversion
SCM/JIRA link daemon commented on JENKINS-15440 Emailing users at the end of a failed build very slow for big Jenkins instance using subversion Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/scm/SubversionMailAddressResolverImpl.java http://jenkins-ci.org/commit/subversion-plugin/b2451c01790b19ab665a880857e641a46ed89828 Log: JENKINS-15440 MailAddressResolverImpl moved to subversion-mail-address-resolver-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15440) Emailing users at the end of a failed build very slow for big Jenkins instance using subversion
Nicolas De Loof commented on JENKINS-15440 Emailing users at the end of a failed build very slow for big Jenkins instance using subversion MailAddressResolverImpl moved to https://github.com/jenkinsci/subversion-mail-address-resolver-plugin, just in case someone want to keep a 100% compatible jenkins. To be released after subversion 1.45 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-15011) Jacoco Plugin 1.0.3 - no threshold config and displays broken graphic link
Ognjen Bubalo commented on JENKINS-15011 Jacoco Plugin 1.0.3 - no threshold config and displays broken graphic link Hi, If you create a new job of your project you should have a good graph. This is a workaround of course. I'll fix it. The main problem is that the plugin was completely refactored, so it is hard to put back the old serialized fields properly. I did not start to work on the threshold feature. It won't take too much time to implment. Currently I'm working on the inclusions, exclusions feature. Cheers, Ogi 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-12497) scm poll not saved when creating a new job
ricktw resolved JENKINS-12497 as Fixed scm poll not saved when creating a new job Not an issue anymore in my Jenkins version (1.493), so marking this issue as Fixed. Change By: ricktw (22/Jan/13 8:55 AM) Status: Open 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
[JIRA] (JENKINS-16427) Job build freezes during access to svn repository
Anton Tupikov commented on JENKINS-16427 Job build freezes during access to svn repository Hello kutzi, thanks for you answer Looks very similar. Now I disabled keyring through ~/.subversion/config and try reproduce the problem. additional question about first recipe: 1. You can disable Keyring for every instance of your program by passing the following system variable: -Dsvnkit.library.gnome-keyring.enabled=false Is it enough run jenkins like java -Dsvnkit.library.gnome-keyring.enabled=false -jar jenkins.war ? 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-15440) Emailing users at the end of a failed build very slow for big Jenkins instance using subversion
kutzi commented on JENKINS-15440 Emailing users at the end of a failed build very slow for big Jenkins instance using subversion Sounds great. I'll push a svn-plugin release today or tomorrow. 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-16319) Failure to delete old config files during rekeying on Windows
cforce commented on JENKINS-16319 Failure to delete old config files during rekeying on Windows Still not released, is 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-9120) RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow
vdupain commented on JENKINS-9120 RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow Same issue on our jenkins (1.499), the stacktrace: Jan 22, 2013 4:11:23 AM winstone.Logger logInternal WARNING: Untrapped Error in Servlet java.lang.ArrayIndexOutOfBoundsException: -255 at hudson.util.RingBufferLogHandler.publish(RingBufferLogHandler.java:52) at java.util.logging.Logger.log(Logger.java:478) at java.util.logging.Logger.doLog(Logger.java:500) at java.util.logging.Logger.logp(Logger.java:616) at java.util.logging.Logger.entering(Logger.java:872) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:155) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) 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-16437) Extract MailAddressResolvers to dedicated plugins
Oliver Gondža created JENKINS-16437 Extract MailAddressResolvers to dedicated plugins Issue Type: Improvement Assignee: Unassigned Components: plugin Created: 22/Jan/13 11:16 AM Description: Extract resolvers into separate plugins to allow administrator to decide which resolvers to use. Project: Jenkins Priority: Major Reporter: Oliver Gondža 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-16438) NullPointerException accessing console
Nicolas De Loof created JENKINS-16438 NullPointerException accessing console Issue Type: Bug Assignee: stevengbrown Components: timestamper Created: 22/Jan/13 11:29 AM Description: ConsoleAnnotator Factory extracts Request.getPathInfo that is null from SRV.11.2 of the Servlet Spec (2.3), if the servlet mapping is "/" then the servletpath should be the uri minus context and pathinfo should be null. it seems tomcat is handling "/*" the same way as "/" (maybe a bug ?) anyway, a defensive null check and fallback to getServletpath would be fine Environment: jenkins deployed on tomcat 6 Project: Jenkins Priority: Major Reporter: Nicolas De Loof 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-16439) 500
Adam Book created JENKINS-16439 500 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: brakeman Created: 22/Jan/13 11:48 AM Description: When trying to set the breakman report options so that the trend graph shows and the warnings will show on clicking save this appears: Status Code: 500 Exception: java.lang.RuntimeException: Failed to serialize hudson.model.Job#properties for class hudson.model.FreeStyleProject Stacktrace: javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize hudson.model.Job#properties for class hudson.model.FreeStyleProject at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) 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:166) 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 org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at
[JIRA] (JENKINS-15472) Option to create a new page
ronny b reopened JENKINS-15472 Option to create a new page I reopened the issue since the change doesn't allow specifying the parent of the new page (as requested in the description). It would be very useful if this could be added. Thanks in advance! Change By: ronny b (22/Jan/13 11:50 AM) Resolution: Fixed Status: Closed 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-3002) TFS Support to get labels
Jeremy McGee edited a comment on JENKINS-3002 TFS Support to get labels As stated by others: I'd like the source for the patch, and I'm happy too to merge back into baseline. jeremy.mc...@bassettdata.com. 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-3002) TFS Support to get labels
Jeremy McGee commented on JENKINS-3002 TFS Support to get labels As stated by others: I'd like the source for the patch, and I'm happy too to merge back into baseline. 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-16439) 500
Richard Mortimer commented on JENKINS-16439 500 The cause of the exception (in the stack trace) is Caused by: java.io.IOException: No space left on device I think on of your filesystems is full. 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-16384) Blocking on downstream projects
cjo9900 commented on JENKINS-16384 Blocking on downstream projects I have managed to reproduce what I think is the issue. and the steps are Trigger A1 A1 triggers B1 Other Jobs triggers E1 Trigger A2 B1 triggers C1, D1 C1, D1 trigger E2 E1 runs A2 runs E2 waits until B2,C2,D2 have finished. In this case I have enabled the Block when upstream is building on project E. and seem to see the same issue as JENKINS-14918 Where E2 is seen as Blocked because E1 is building The the queue is processed in order with A2 checked first and E2 is still classed as blocked so A2 is run. Then E2 is checked and still blocked due A2 running. Can you check the settings for Job E and see if this is the case. 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-16409) Add a Script trigger
Sebastian Schuberth commented on JENKINS-16409 Add a Script trigger Ah, thanks, I guess that would do the job, so feel free to close this. 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-16409) Add a Script trigger
Slide-O-Mix resolved JENKINS-16409 as Not A Defect Add a Script trigger Change By: Slide-O-Mix (22/Jan/13 12:27 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-16319) Failure to delete old config files during rekeying on Windows
Damien Finck commented on JENKINS-16319 Failure to delete old config files during rekeying on Windows @cforce : You can see the changelog : http://jenkins-ci.org/changelog "Upcomming changes" "Rekeying operation (from SECURITY-49 fix in 1.498) failed on Windows. (issue 16319)" The fix will be in 1.501 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-16427) Job build freezes during access to svn repository
kutzi commented on JENKINS-16427 Job build freezes during access to svn repository I don't know. Depending on how you start your 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-10100) Replace build-in test graphs with the TestNG ones
kutzi commented on JENKINS-10100 Replace build-in test graphs with the TestNG ones To be honest, I don't remember if I posted this question to the dev-list at all. And if I did, I think I didn't get any answer. The answer would probably be a new @Extension point in Jenkins core. 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-16404) email-ext regression trigger not firing when it should
Michał Guminiak commented on JENKINS-16404 email-ext regression trigger not firing when it should I'm seeing something similar in email-ext 2.24.1 and Jenkins 1.480.1. My failed and unstable triggers work ok, but it doesn't seem to catch regressions. The logs does not contain anything useful either... Could you post any workarounds if you find any? 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-16440) Please add an indication that scm is ahead of current release
Marek Nazarko created JENKINS-16440 Please add an indication that scm is ahead of current release Issue Type: Improvement Affects Versions: current Assignee: Fred G Components: extra-columns Created: 22/Jan/13 12:50 PM Description: Could it be possible to add an indicator that there are new commits after a build has been released? Something like "new changes arrived". In git it could be as easy as comparing last build git sha1 with current one. The best would be to have different indicator for release and snapshot Project: Jenkins Priority: Major Reporter: Marek Nazarko 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-16441) Scm sync fails completely if folder name starts with a hyphen
Gábor Karsai created JENKINS-16441 Scm sync fails completely if folder name starts with a hyphen Issue Type: Bug Affects Versions: current Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 22/Jan/13 12:53 PM Description: If the jenkins job name starts with a hyphen, then the job deletion fails. And after that the syncing is stopped, plugin can't recover from the failure. Manual git sync, and deletion and restart required to fix the problem. Environment: Ubuntu 12.04, Jenkins 1.498, Plugin 0.0.6.1, GIT 1.7.9.5 as SCM, GIT smart-http over ssl. Project: Jenkins Labels: plugin git Priority: Minor Reporter: Gábor Karsai 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-16441) Scm sync fails completely if folder name starts with a hyphen
Gábor Karsai updated JENKINS-16441 Scm sync fails completely if folder name starts with a hyphen Change By: Gábor Karsai (22/Jan/13 12:53 PM) Description: Ifthejenkinsjobnamestartswithahyphen,thenthejobdeletionfails.Andafterthatthesyncingisstopped,plugincantrecoverfromthefailure.Manualgitsync,anddeletionand jenkins restartrequiredtofixtheproblem. 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-16404) email-ext regression trigger not firing when it should
Slide-O-Mix commented on JENKINS-16404 email-ext regression trigger not firing when it should There wouldn't be any workarounds...there seems to be a code 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
[JIRA] (JENKINS-16404) email-ext regression trigger not firing when it should
Michał Guminiak commented on JENKINS-16404 email-ext regression trigger not firing when it should I would also like to suggest that if one test is fixed and another is broken between builds it should still count as a regression I guess... Maybe we could check if there is a failing test with age 1 and then trigger the regression email? 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-16404) email-ext regression trigger not firing when it should
Slide-O-Mix commented on JENKINS-16404 email-ext regression trigger not firing when it should If you are familiar with Java, you could fork the plugin on GitHub, make and test the changes and issue a pull request. It may get done sooner that way 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-16442) Jira Login always requires Admin reset
Chris Engler created JENKINS-16442 Jira Login always requires Admin reset Issue Type: Bug Assignee: Unassigned Components: jira Created: 22/Jan/13 2:07 PM Description: Everytime I want to log into Jira, I have to request a password reset. I've made simple passwords that were accepted in the password reset dialog, but failed to work after log out and sign on. Environment: Windows XP Browser IE 8 Project: Jenkins Priority: Major Reporter: Chris Engler 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-16443) Multiple LDAP server
chirag Patel created JENKINS-16443 Multiple LDAP server Issue Type: Improvement Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ldap Created: 22/Jan/13 2:13 PM Description: Cannot add multiple LDAP servers, Current version will only let you add one LDAP server it should let you add more then one LDAP server Environment: WIndows Project: Jenkins Labels: plugin Priority: Major Reporter: chirag Patel 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-1489) JIRA plugin - security level for comment
gecon27 commented on JENKINS-1489 JIRA plugin - security level for comment Hello, We get the following error when adding a JIRA group in Jenkins for comment visibility: Updating JIRA-1234 Looks like JIRA-1234 is no valid JIRA issue or you don't have permission to update the issue. Issue will not be updated. com.atlassian.jira.rpc.exception.RemotePermissionException: You do not have permission to get a group. Is it necessary that the JIRA user configured on Jenkins has global admin rights? Why is the plugin calling getGroup() - which indeed most probably does require global admin rights, rather than just set directly the JIRA group on the comment object level? Thanks, Ioannis 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-4561) Delete All Disabled Modules Not visible for project users
evernat commented on JENKINS-4561 Delete All Disabled Modules Not visible for project users Is it reproduced with a recent Jenkins version? 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-16438) NullPointerException accessing console
stevengbrown resolved JENKINS-16438 as Fixed NullPointerException accessing console Thanks for the well-researched bug report. Let me know if Timestamper 1.5.1 works for you. Change By: stevengbrown (22/Jan/13 3:31 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16436) Build - Prerequisites Check
Larry Shatzer, Jr. assigned JENKINS-16436 to Unassigned Build - Prerequisites Check Change By: Larry Shatzer, Jr. (22/Jan/13 3:35 PM) Assignee: LarryShatzer,Jr. 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-4561) Delete All Disabled Modules Not visible for project users
pkorzuszek commented on JENKINS-4561 Delete All Disabled Modules Not visible for project users Is it reproduced with a recent Jenkins version? Yes, it is (Jenkins 1.499). 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-16438) NullPointerException accessing console
SCM/JIRA link daemon commented on JENKINS-16438 NullPointerException accessing console Code changed in jenkins User: StevenGBrown Path: src/main/java/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory.java http://jenkins-ci.org/commit/timestamper-plugin/9ca1cfa3a5b7144cbb009f261918bfa115b3301f Log: FIXED JENKINS-16438 Fall back to servlet path when no path info 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-16444) NPE from BuildTrigger$DescriptorImpl.showEvenIfUnstableOption
Jesse Glick created JENKINS-16444 NPE from BuildTrigger$DescriptorImpl.showEvenIfUnstableOption Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Jan/13 4:05 PM Description: In 1.480.2 and 1.500-SNAPSHOT, get an exception while adding a new Build other projects post-build action: … hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: descriptor.showEvenIfUnstableOption(targetType). Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.tasks.BuildTrigger$DescriptorImpl.showEvenIfUnstableOption(BuildTrigger.java:315) 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:601) 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:72) 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.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.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.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) 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.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) 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.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at hudson.widgets.RenderOnDemandClosure$1.generateResponse(RenderOnDemandClosure.java:91) … Project: Jenkins Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you
[JIRA] (JENKINS-16444) NPE from BuildTrigger$DescriptorImpl.showEvenIfUnstableOption
Jesse Glick
updated JENKINS-16444
NPE from BuildTrigger$DescriptorImpl.showEvenIfUnstableOption
Change By:
Jesse Glick
(22/Jan/13 4:06 PM)
Description:
In1.480.2and1.500-SNAPSHOT,getanexceptionwhileaddinganew*Buildotherprojects*post-buildaction
toafreestyleproject
:{code:none}…hudson.ExpressionFactory2$JexlExpressionevaluateWARNING:Caughtexceptionevaluating:descriptor.showEvenIfUnstableOption(targetType).Reason:java.lang.NullPointerExceptionjava.lang.NullPointerException athudson.tasks.BuildTrigger$DescriptorImpl.showEvenIfUnstableOption(BuildTrigger.java:315) atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:601) atorg.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) atorg.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) atorg.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) atorg.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) atorg.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) atorg.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) athudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72) atorg.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) atorg.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsBoolean(ExpressionSupport.java:71) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:97) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) atorg.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) atorg.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) atorg.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) atorg.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) atorg.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) atorg.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) atorg.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) atorg.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) atorg.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) atorg.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) athudson.widgets.RenderOnDemandClosure$1.generateResponse(RenderOnDemandClosure.java:91) …{code}
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-777) The need for Subversion command line options.
Ben Zimmerman commented on JENKINS-777 The need for Subversion command line options. Is there a planned release date for Subverion Plugin v1.45, which contains this fix? On the wiki page, it only indicates "Upcoming" for v1.45. 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-16444) NPE from BuildTrigger$DescriptorImpl.showEvenIfUnstableOption
SCM/JIRA link daemon commented on JENKINS-16444 NPE from BuildTrigger$DescriptorImpl.showEvenIfUnstableOption Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/tasks/BuildTrigger.java core/src/main/resources/hudson/tasks/BuildTrigger/config.jelly http://jenkins-ci.org/commit/jenkins/0bdde83cbb18300d555dda4e7f0ee663f4ad267f Log: FIXED JENKINS-16444 NPE showEvenIfUnstableOption when first adding trigger section. At this time the target project is unset so it has no known type and we just have to assume the threshold is valid. Compare: https://github.com/jenkinsci/jenkins/compare/a1e709ddf0ca...0bdde83cbb18 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-16444) NPE from BuildTrigger$DescriptorImpl.showEvenIfUnstableOption
SCM/JIRA link daemon resolved JENKINS-16444 as Fixed NPE from BuildTrigger$DescriptorImpl.showEvenIfUnstableOption Change By: SCM/JIRA link daemon (22/Jan/13 5:00 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16444) NPE from BuildTrigger$DescriptorImpl.showEvenIfUnstableOption
SCM/JIRA link daemon commented on JENKINS-16444 NPE from BuildTrigger$DescriptorImpl.showEvenIfUnstableOption Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/ExpressionFactory2.java http://jenkins-ci.org/commit/jenkins/810a3954cc07eb0561ee201d4a1e8efeb41d18a1 Log: JENKINS-16444 Diagnostics useful for this and similar exceptions during Jelly evaluation. 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-16444) NPE from BuildTrigger$DescriptorImpl.showEvenIfUnstableOption
dogfood commented on JENKINS-16444 NPE from BuildTrigger$DescriptorImpl.showEvenIfUnstableOption Integrated in jenkins_main_trunk #2207 JENKINS-16444 Diagnostics useful for this and similar exceptions during Jelly evaluation. (Revision 810a3954cc07eb0561ee201d4a1e8efeb41d18a1) FIXED JENKINS-16444 NPE showEvenIfUnstableOption when first adding trigger section. (Revision 0bdde83cbb18300d555dda4e7f0ee663f4ad267f) Result = SUCCESS Jesse Glick : 810a3954cc07eb0561ee201d4a1e8efeb41d18a1 Files : core/src/main/java/hudson/ExpressionFactory2.java Jesse Glick : 0bdde83cbb18300d555dda4e7f0ee663f4ad267f Files : core/src/main/resources/hudson/tasks/BuildTrigger/config.jelly core/src/main/java/hudson/tasks/BuildTrigger.java changelog.html 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-16069) Combobox component broken since 1.480
Jesse Glick updated JENKINS-16069 Combobox component broken since 1.480 Potentially worth backporting to 1.480.x. What caused the regression? I am guessing the fix of JENKINS-13541. The fix simply reverts commit 106d95a79f86f81d16ea66a8ea1a33aea9e85773 Author: kohsuke kohsuke@71c3de6d-444a-0410-be80-ed276b4c234a Date: Tue Sep 28 21:11:09 2010 + Prototype.js calls eval() on the response when the content type is set to _javascript_, and eval() fails without the surrounding bracket. Change By: Jesse Glick (22/Jan/13 6:14 PM) Priority: Major Critical 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-16069) Combobox component broken since 1.480
Jesse Glick edited a comment on JENKINS-16069 Combobox component broken since 1.480 Potentially worth backporting to 1.480.x. What caused the regression? I am guessing the fix of JENKINS-13541. The fix of this issue simply reverts commit 106d95a79f86f81d16ea66a8ea1a33aea9e85773 Author: kohsuke kohsuke@71c3de6d-444a-0410-be80-ed276b4c234a Date: Tue Sep 28 21:11:09 2010 + Prototype.js calls eval() on the response when the content type is set to _javascript_, and eval() fails without the surrounding bracket. 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-16069) Combobox component broken since 1.480
Vincent Latombe commented on JENKINS-16069 Combobox component broken since 1.480 I don't exactly know where the regression took place. Probably in the process of componentization that took place back in 1.480 something changed on the _javascript_ side of json parsing. 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-14529) BindException when using --daemon with JMX
Jesse Glick started work on JENKINS-14529 BindException when using --daemon with JMX Change By: Jesse Glick (22/Jan/13 7:28 PM) 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
[JIRA] (JENKINS-14529) BindException when using --daemon with JMX
Jesse Glick commented on JENKINS-14529 BindException when using --daemon with JMX https://github.com/kohsuke/akuma/pull/4 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-13541) Content Type of JSON API responses is not 'application/json'
SCM/JIRA link daemon commented on JENKINS-13541 Content Type of JSON API responses is not application/json Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/bb3be8314cc04c54838331da088d35e46b68a224 Log: JENKINS-13541 Noting. 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-16130) Please provide folder links on build results page to condense long file paths
Fabio Sobral commented on JENKINS-16130 Please provide folder links on build results page to condense long file paths I just tried using ArtifactDeployer to move the archived files outside the JENKINS_HOME and it worked as expected, but the plugin output is a critical issue for me. My biggest job archives thousands of files which makes the current output unusable. The lack of the "view" option is also a problem. I'm looking forward for this issue to be solved, but until then I'll have to keep moving old archived files from JENKINS_HOME the old way. 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-13541) Content Type of JSON API responses is not 'application/json'
dogfood commented on JENKINS-13541 Content Type of JSON API responses is not application/json Integrated in jenkins_main_trunk #2208 JENKINS-13541 Noting. (Revision bb3be8314cc04c54838331da088d35e46b68a224) Result = SUCCESS Jesse Glick : bb3be8314cc04c54838331da088d35e46b68a224 Files : changelog.html 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-777) The need for Subversion command line options.
kutzi commented on JENKINS-777 The need for Subversion command line options. I just did the release. Should be available in the update center soon. 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-16273) Slaves forbidden to request JNLP anonymously but -jnlpCredentials not offered
Jesse Glick commented on JENKINS-16273 Slaves forbidden to request JNLP anonymously but -jnlpCredentials not offered @nerdmachine there is no need to run without security; you just need to manually specify -jnlpCredentials user:apitoken in jenkins-slave.xml. The SECURITY project is indeed restricted. See https://wiki.jenkins-ci.org/display/JENKINS/Security+Advisories for information. 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-16069) Combobox component broken since 1.480
Jesse Glick commented on JENKINS-16069 Combobox component broken since 1.480 @vlatombe my guess is that JENKINS-13541 was the cause; this was in 1.471. Have not yet bisected to be sure. 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-16341) Memory leak in createJavaScriptProxy
Kohsuke Kawaguchi commented on JENKINS-16341 Memory leak in createJavaScriptProxy The other thing that helps is to make proxies have well-known URLs. If the fragment rendered on-demand do not depend on the request context (or if it can be recreated from future requests), then there won't be any need to keep session-scoped objects. Some of the core tags might very well fit with this, since they explicitly lists variables that get captured. But otherwise I agree that ping is the only way I can think of. 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-16341) Memory leak in createJavaScriptProxy
Jesse Glick commented on JENKINS-16341 Memory leak in createJavaScriptProxy RenderOnDemandClosure cannot be done this way AFAICT, since its variables are of unrestricted type. Nor can other uses of @_javascript_Method, unless we can somehow establish that the receiver object is a singleton. 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-16341) Memory leak in createJavaScriptProxy
Jesse Glick commented on JENKINS-16341 Memory leak in createJavaScriptProxy @kohsuke points out that WithWellKnownURL may be used for singleton objects with a @_javascript_Method to avoid this bug. That is no help for l:renderOnDemand. 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-16440) Please add an indication that scm is ahead of current release
Fred G assigned JENKINS-16440 to Marek Nazarko Please add an indication that scm is ahead of current release Change By: Fred G (22/Jan/13 10:06 PM) Assignee: FredG MarekNazarko 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-16440) Please add an indication that scm is ahead of current release
Fred G commented on JENKINS-16440 Please add an indication that scm is ahead of current release Could you explain the use-case a bit more? What would you do if you see a "new changes arrived" indication? Start the build manually? Not sure if you saw this, but a new plugin has just been created yesterday, that seems to fit your description: https://wiki.jenkins-ci.org/display/JENKINS/Pending+Changes+Plugin Maybe this plugin already has some sort of notification (eg. Email) built-in. This could be faster and simpler than manually checking an indication in a column. Or it provides a common interface that can be used by other plugins. 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-12511) WORKSPACE variable wrong in case Jenkins did an automatic extension to the workspace path like 'workspace path@2', e.g. when running concurrent builds
evernat commented on JENKINS-12511 WORKSPACE variable wrong in case Jenkins did an automatic extension to the workspace path like workspace path@2, e.g. when running concurrent builds Is it reproduced with a recent Jenkins version? 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-13978) Add posibility to copy view
Derek Brown commented on JENKINS-13978 Add posibility to copy view I would use this feature every time I branch my projects. I would be using it today if it existed. Derek. . . 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-16440) Please add an indication that scm is ahead of current release
Marek Nazarko commented on JENKINS-16440 Please add an indication that scm is ahead of current release I have many projects which depends on themselves, but they aren't multimodule project. Releasing everything to have the newest possible combo isn't good idea - I don't want to release if there were no changes. Plus there is need to commit every pom with upped version of every dependency - so it is good to release only when neccessary. I didn't notice Pending Changes Plugin and don't see there is anything to read about. Unfortunatelly git plugin doesn't offer any extension point to read for example last sha1, but it is rather easy to do manually. I was also thinking about something like triggering build from commit hook - but instead of building show only indication that there is something new committed. But it needs some api form jenkins. 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
eguess74
commented on JENKINS-15779
Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
I applied the patch to the current master and assembled the plugin - it works when running on master and fails on a slave with NPE
Parsing Ivy Descriptor Files
Error while reading the default Ivy 2.1 settings: failed to load settings from file:../custom.ivy.settings.xml: io problem while parsing config file: ../custom.ivy.settings-${ENV.JAVA_VERSION}.xml
[Ljava.lang.StackTraceElement;@10a6bf3
ERROR: Failed to parse ivy.xml files
java.io.IOException: Unable to parse ivy descriptors
at hudson.ivy.IvyModuleSetBuild$RunnerImpl.parseIvyDescriptorFiles(IvyModuleSetBuild.java:530)
at hudson.ivy.IvyModuleSetBuild$RunnerImpl.doRun(IvyModuleSetBuild.java:366)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:589)
at hudson.model.Run.execute(Run.java:1516)
at hudson.model.Run.run(Run.java:1462)
at hudson.ivy.IvyModuleSetBuild.run(IvyModuleSetBuild.java:282)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
Caused by: java.lang.NullPointerException
at hudson.ivy.IvyModuleSetBuild$IvyXmlParser.call(IvyModuleSetBuild.java:793)
at hudson.ivy.IvyModuleSetBuild$IvyXmlParser.call(IvyModuleSetBuild.java:742)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
eguess74
edited a comment on JENKINS-15779
Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
I applied the patch to the current master and assembled the plugin - it works when running on master and fails on a slave with NPE
Parsing Ivy Descriptor Files
Error while reading the default Ivy 2.1 settings: failed to load settings from file:../custom.ivy.settings.xml: io problem while parsing config file: ../custom.ivy.settings-${ENV.JAVA_VERSION}.xml
[Ljava.lang.StackTraceElement;@10a6bf3
ERROR: Failed to parse ivy.xml files
java.io.IOException: Unable to parse ivy descriptors
at hudson.ivy.IvyModuleSetBuild$RunnerImpl.parseIvyDescriptorFiles(IvyModuleSetBuild.java:530)
at hudson.ivy.IvyModuleSetBuild$RunnerImpl.doRun(IvyModuleSetBuild.java:366)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:589)
at hudson.model.Run.execute(Run.java:1516)
at hudson.model.Run.run(Run.java:1462)
at hudson.ivy.IvyModuleSetBuild.run(IvyModuleSetBuild.java:282)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
Caused by: java.lang.NullPointerException
at hudson.ivy.IvyModuleSetBuild$IvyXmlParser.call(IvyModuleSetBuild.java:793)
at hudson.ivy.IvyModuleSetBuild$IvyXmlParser.call(IvyModuleSetBuild.java:742)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford
commented on JENKINS-15779
Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Where is custom.ivy.settings-${ENV.JAVA_VERSION}.xml defined? Have you set it in "Ivy settings property files"?
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-14529) BindException when using --daemon with JMX
SCM/JIRA link daemon commented on JENKINS-14529 BindException when using --daemon with JMX Code changed in jenkins User: Jesse Glick Path: changelog.html core/pom.xml http://jenkins-ci.org/commit/jenkins/61d46127be97545368b6a95bf0cb05d01aa80663 Log: FIXED JENKINS-14529 BindException when using --daemon with JMX. 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-14529) BindException when using --daemon with JMX
SCM/JIRA link daemon resolved JENKINS-14529 as Fixed BindException when using --daemon with JMX Change By: SCM/JIRA link daemon (22/Jan/13 11:52 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
[JIRA] (JENKINS-16430) Cannot connect a slave without Connect right
Jesse Glick resolved JENKINS-16430 as Not A Defect Cannot connect a slave without Connect right Right. See JENKINS-16273 for discussion. Change By: Jesse Glick (23/Jan/13 12:04 AM) 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-16310) Source code loses spacing/indenting due to html white space collapsing.
Ognjen Bubalo started work on JENKINS-16310 Source code loses spacing/indenting due to html white space collapsing. Change By: Ognjen Bubalo (23/Jan/13 12:34 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
[JIRA] (JENKINS-14529) BindException when using --daemon with JMX
dogfood commented on JENKINS-14529 BindException when using --daemon with JMX Integrated in jenkins_main_trunk #2209 FIXED JENKINS-14529 BindException when using --daemon with JMX. (Revision 61d46127be97545368b6a95bf0cb05d01aa80663) Result = SUCCESS Jesse Glick : 61d46127be97545368b6a95bf0cb05d01aa80663 Files : changelog.html core/pom.xml 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-13553) Deleting project workspace Plugin: Jenkins hudson.Util.deleteFile Error
Alexey Gavrilov commented on JENKINS-13553 Deleting project workspace Plugin: Jenkins hudson.Util.deleteFile Error I also experience the same problem. Jenkins 1.492, WsCleanup 0.10 Here is the extract fro the log: Deleting project workspace... ERROR: Publisher hudson.plugins.ws_cleanup.WsCleanup aborted due to exception java.lang.UnsupportedOperationException: Failed to link the library: interface hudson.util.jna.Kernel32 at hudson.util.jna.InitializationErrorInvocationHandler.invoke(InitializationErrorInvocationHandler.java:28) at $Proxy7.GetFileAttributesW(Unknown Source) at hudson.util.jna.Kernel32Utils.getWin32FileAttributes(Kernel32Utils.java:76) at hudson.util.jna.Kernel32Utils.isJunctionOrSymlink(Kernel32Utils.java:80) at hudson.Util.isSymlink(Util.java:322) at hudson.Util.deleteRecursive(Util.java:283) at hudson.plugins.ws_cleanup.Cleanup.invoke(Cleanup.java:60) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2309) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:60) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.UnsatisfiedLinkError: Unable to load library 'kernel32': com.sun.jna.Native.open(Ljava/lang/String;)J at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:166) at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:239) at com.sun.jna.Library$Handler.init(Library.java:140) at com.sun.jna.Native.loadLibrary(Native.java:366) at com.sun.jna.Native.loadLibrary(Native.java:351) at hudson.util.jna.Kernel32Utils.load(Kernel32Utils.java:85) at hudson.util.jna.Kernel32.clinit(Kernel32.java:37) at hudson.util.jna.Kernel32Utils.getWin32FileAttributes(Kernel32Utils.java:76) at hudson.util.jna.Kernel32Utils.isJunctionOrSymlink(Kernel32Utils.java:80) at hudson.Util.isSymlink(Util.java:322) at hudson.plugins.disk_usage.DiskUsageThread$DiskUsageCallable.getFileSize(DiskUsageThread.java:168) at hudson.plugins.disk_usage.DiskUsageThread$DiskUsageCallable.call(DiskUsageThread.java:162) at hudson.plugins.disk_usage.DiskUsageThread$DiskUsageCallable.call(DiskUsageThread.java:149) ... 10 more 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-13218) Can't add build step on current jenkins with manual installed buckminster 3.7
Andreas Schilling commented on JENKINS-13218 Cant add build step on current jenkins with manual installed buckminster 3.7 Any chance to fix that? We can usually work around it by using IE, but not everyone is on Windows and often you forget to tell your new colleagues and they fail managing their 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-15156) Builds Disappear from Build History after Completion
domi assigned JENKINS-15156 to Jesse Glick Builds Disappear from Build History after Completion Sorry Jesse, I'm assigning this to you so that some more core devs are aware of this one... Change By: domi (23/Jan/13 7:21 AM) Assignee: JesseGlick 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-16446) NPE in projectView when not logged in
Magnus Jacobsson created JENKINS-16446 NPE in projectView when not logged in Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 23/Jan/13 7:34 AM Description: NullPointerException when accessing any view without being logged in. When logged in it's ok. Accessing other parts of Jenkins than the views is ok. Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.499.jar!/hudson/model/View/index.jelly:44:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.499.jar!/lib/hudson/projectView.jelly:64:22: d:invokeBody java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.499.jar!/hudson/model/View/index.jelly:44:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.499.jar!/lib/hudson/projectView.jelly:64:22: d:invokeBody java.lang.NullPointerException at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:562) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) 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:166) 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 org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] (JENKINS-16447) Fix polling display: Show ANY instead of null
Mads Nielsen created JENKINS-16447 Fix polling display: Show ANY instead of null Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: clearcase-ucm Created: 23/Jan/13 7:49 AM Project: Jenkins Priority: Trivial Reporter: Mads Nielsen 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
