[JIRA] [flexible-publish] (JENKINS-25017) BuildTrigger in Flexible Publish doesn't work since Jenkins 1.501
wernight commented on JENKINS-25017 BuildTrigger in Flexible Publish doesnt work since Jenkins 1.501 I confirm the workaround (using Parameterized Trigger together with Flexible Trigger) to be working. 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] [flexible-publish] (JENKINS-25017) BuildTrigger in Flexible Publish doesn't work since Jenkins 1.501
wernight commented on JENKINS-25017 BuildTrigger in Flexible Publish doesnt work since Jenkins 1.501 Thanks for taking a look. I cannot use "Parameterized Trigger" from within a Flexible block (I see no such option). Using just Parameterized Trigger works, but it's unconditional. 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] [flexible-publish] (JENKINS-25017) Not triggering other job
wernight created JENKINS-25017 Not triggering other job Issue Type: Bug Assignee: bap Components: flexible-publish Created: 07/Oct/14 9:21 AM Description: Config set to "Build other projects" (trigger only if build is stable) Log shows: Strings match run condition: string 1=ref-updated, string 2=ref-updated Strings match run condition: string 1=master, string 2=master Run condition And enabling perform for step Build other projects It's the last step and build is stable, but the other job is NOT triggered. The other job takes one optional argument, but it's never triggered by this plugin. Project: Jenkins Priority: Major Reporter: wernight 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] [flexible-publish] (JENKINS-25017) Not triggering other job
wernight commented on JENKINS-25017 Not triggering other job I created an new job with only this plugins and it still doesn't trigger: Building on master in workspace /var/lib/jenkins/jobs/dummy/workspace Run condition Always enabling prebuild for step Build other projects Run condition Always enabling perform for step Build other projects Finished: SUCCESS 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] [flexible-publish] (JENKINS-25017) Not triggering other job
wernight edited a comment on JENKINS-25017 Not triggering other job I created an new job with only this plugins and it still doesn't trigger: Building on master in workspace /var/lib/jenkins/jobs/dummy/workspace Run condition Always enabling prebuild for step Build other projects Run condition Always enabling perform for step Build other projects Finished: SUCCESS Also Jenkins log shows no error. 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] [flexible-publish] (JENKINS-25017) Not triggering other job
wernight updated JENKINS-25017 Not triggering other job Change By: wernight (07/Oct/14 9:40 AM) Environment: Jenkins1.583 Priority: Major Critical Labels: 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] [git] (JENKINS-21521) Submodules are disabled by default as of git plugin 2.0.1
wernight commented on JENKINS-21521 Submodules are disabled by default as of git plugin 2.0.1 That's actually NOT a minor issue as it break existing products and makes setup much harder. Submodules are an important part of Git and should be checked. 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] [gerrit-trigger] (JENKINS-15654) Trigger on reason provided so as to change behavior for change-merged
wernight resolved JENKINS-15654 as Fixed Trigger on reason provided so as to change behavior for change-merged Yes the GERRIT_EVENT_TYPE is can help to tell that. I think I submitted this before that change. I'll try again to couple it with the Promoted Builds Plugin. Change By: wernight (15/Jul/13 11:53 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-13910) git plugin: 'clean after checkout does not git clean -fdx on submodules
wernight commented on JENKINS-13910 git plugin: clean after checkout does not git clean -fdx on submodules It seems that it's not doing a 'git clean -fdx' even on the main checkout. We have files left over. Versions: Jenkins GIT client plugin 1.0.7 Jenkins GIT plugin 1.4.0 Git server plugin 1.1 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] [release] (JENKINS-10551) Check the parameter from upstream job to trigger a release build
wernight commented on JENKINS-10551 Check the parameter from upstream job to trigger a release build The main reason I'd use a release trigger is to have a release done when for example a change goes into a SCC branch or a Gerrit commit is merged into master. 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] [instant-messaging] (JENKINS-18144) Allow templating or reduce verbosity
wernight created JENKINS-18144 Allow templating or reduce verbosity Issue Type: Improvement Assignee: kutzi Components: instant-messaging Created: 30/May/13 12:52 PM Description: Typical summary log is: Project Example build #1234: STILL UNSTABLE in 1 min 12 sec: http://example.com/job/Example/1234/ The time for example is completely irrelevant for me in most cases. I usually wish only to see how many tests fails if it's unstable but else I really just care SUCCESS/FAILED. One way would be to hard code with a bit more succinct message. Another way would be to allow templating the message: Project $PROJECT_NAME build $BUILD_NUMBER: $STATUS: $PROJECT_URL $TESTS_RESULTS Project: Jenkins Priority: Minor Reporter: wernight 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] [active-directory] (JENKINS-8119) Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user 'kgraham' or incorrect password, when 1.16 does
wernight reopened JENKINS-8119 Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user kgraham or incorrect password, when 1.16 does not Same issue after upgrading from 1.2 to 1.4. Note that my LDAP password may have changed in the mean time. Change By: wernight (03/May/13 5:08 PM) Resolution: CannotReproduce Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [active-directory] (JENKINS-8119) Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user 'kgraham' or incorrect password, when 1.16 does
wernight edited a comment on JENKINS-8119 Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user kgraham or incorrect password, when 1.16 does not Similar issue after upgrading from 1.2 to 1.4. Note that my LDAP password may have changed in the mean time. org.acegisecurity.BadCredentialsException: Incorrect password for XXX for="" Doe,OU=XX...: error=8007203A; nested exception is com4j.ComException: 8007203a The server is not operational. : The server is not operational. : .\invoke.cpp:517 at hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:109) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:30) at org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.loadUserDetails(TokenBasedRememberMeServices.java:308) at org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.autoLogin(TokenBasedRememberMeServices.java:218) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$1.autoLogin(ActiveDirectorySecurityRealm.java:140) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:104) 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:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) 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 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:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: com4j.ComException: 8007203a The server is not operational. : The server is not operational. : .\invoke.cpp:517 at com4j.Wrapper.invoke(Wrapper.java:166) at $Proxy43.openDSObject(Unknown Source) at hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:101) ... 35 more Caused by: com4j.ComException: 8007203a The server is not operational. : The server is not operational. : .\invoke.cpp:517 at com4j.Native.invoke(Native Method) at com4j.StandardComMethod.invoke(StandardComMethod.java:35) at com4j.Wrapper$InvocationThunk.call(Wrapper.java:340) at com4j.Task.invoke(Task.java:51) at com4j.ComThread.run0(ComThread.java:153) at com4j.ComThread.run(ComThread.java:134)
[JIRA] [active-directory] (JENKINS-8119) Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user 'kgraham' or incorrect password, when 1.16 does
wernight edited a comment on JENKINS-8119 Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user kgraham or incorrect password, when 1.16 does not Similar issue after upgrading from 1.30 to 1.32. Note that my LDAP password may have changed in the mean time. org.acegisecurity.BadCredentialsException: Incorrect password for XXX for=CN=John Doe,OU=XX...: error=8007203A; nested exception is com4j.ComException: 8007203a The server is not operational. : The server is not operational. : .\invoke.cpp:517 at hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:109) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:30) at org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.loadUserDetails(TokenBasedRememberMeServices.java:308) at org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.autoLogin(TokenBasedRememberMeServices.java:218) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$1.autoLogin(ActiveDirectorySecurityRealm.java:140) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:104) 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:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) 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 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:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: com4j.ComException: 8007203a The server is not operational. : The server is not operational. : .\invoke.cpp:517 at com4j.Wrapper.invoke(Wrapper.java:166) at $Proxy43.openDSObject(Unknown Source) at hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:101) ... 35 more Caused by: com4j.ComException: 8007203a The server is not operational. : The server is not operational. : .\invoke.cpp:517 at com4j.Native.invoke(Native Method) at com4j.StandardComMethod.invoke(StandardComMethod.java:35) at com4j.Wrapper$InvocationThunk.call(Wrapper.java:340) at com4j.Task.invoke(Task.java:51) at com4j.ComThread.run0(ComThread.java:153) at com4j.ComThread.run(ComThread.java:134) Note that deleting my cookies allows me to see the page but then the login just says invalid
[JIRA] [core] (JENKINS-9920) Aggregated test result chart doesn't display test results of the aggregating job
wernight edited a comment on JENKINS-9920 Aggregated test result chart doesnt display test results of the aggregating job This is also something I'd like to see as there is no other simple fix especially if job A archives artifacts used by B. For example: Job A compiles and runs unit tests Job B runs system tests on another Jenkins node Both jobs generate xUnit reports but B must run after A has archived artifacts A should report xUnit reports of itself and B. Currently it can only report xUnit reports of itself (x)or B. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9920) Aggregated test result chart doesn't display test results of the aggregating job
wernight commented on JENKINS-9920 Aggregated test result chart doesnt display test results of the aggregating job This is also something I'd like to see as there is no other simple fix especially if job A archives artifacts used by B. For example A builds and runs unit tests, while B runs system tests on another Jenkins node; both report xUnit but B must run AFTER A has Archived artifacts, and A should report xUnit reports of itself and B. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9920) Aggregated test result chart doesn't display test results of the aggregating job
wernight edited a comment on JENKINS-9920 Aggregated test result chart doesnt display test results of the aggregating job This is also something I'd like to see as there is no other simple fix especially if job A archives artifacts used by B. For example A compiles and runs unit tests, while B runs system tests on another Jenkins node; both jobs generate xUnit reports but B must run AFTER A has archived artifacts, and A should report xUnit reports of itself and B. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16823) Successful even when it fails to delete files
wernight created JENKINS-16823 Successful even when it fails to delete files Issue Type: Bug Assignee: vjuranek Components: ws-cleanup Created: 15/Feb/13 10:57 AM Description: 1. Keep a file open (e.g., a zip) 2. Run clean workspace Expecting: Cannot delete file x.zip log message Build failure I'd hope there would be one or two retry after a few seconds (some coporate anti-virus, Symantec, like have a tendency to keep files open). Project: Jenkins Priority: Critical Reporter: wernight This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16823) Successful even when it fails to delete files
wernight
commented on JENKINS-16823
Successful even when it fails to delete files
I saw the plugin uses ws.deleteContents() in PreBuildCleanup (I did a pre-build clean-up) which should be equivalent to:
new FilePath(new File('D:\\Jenkins\\workspace\\test')).deleteContents();
I'm not sure why this one doesn't use deleteRecursive() by default like the post-build clean-up. Running that command in Groovy throws a java.io.IOException which it should. It seems that the catching of the exception doesn't actually print anything in the log:
} catch (IOException e) {
Logger.getLogger(PreBuildCleanup.class.getName()).log(Level.SEVERE, null, e);
e.printStackTrace();
} ...
Possibly it should throw a AbortException and log properly the error.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16823) Successful even when it fails to delete files
wernight started work on JENKINS-16823 Successful even when it fails to delete files Change By: wernight (15/Feb/13 1:57 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16823) Successful even when it fails to delete files
wernight started work on JENKINS-16823 Successful even when it fails to delete files Change By: wernight (15/Feb/13 1:57 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16823) Successful even when it fails to delete files
wernight stopped work on JENKINS-16823 Successful even when it fails to delete files Change By: wernight (15/Feb/13 1:57 PM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16823) Successful even when it fails to delete files
wernight assigned JENKINS-16823 to wernight Successful even when it fails to delete files Change By: wernight (15/Feb/13 1:57 PM) Assignee: vjuranek wernight This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16823) Successful even when it fails to delete files
wernight resolved JENKINS-16823 as Fixed Successful even when it fails to delete files I've sent a GitHub pull request with two patches. One to fix this issue, one that retries 3 times to delete at 3 seconds interval. The second one has only been applied to the pre-build yet. I'd suggest to refactor so that pre-build and post-build use the same class to do the actual job. Change By: wernight (15/Feb/13 3:06 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/groups/opt_out.
[JIRA] (JENKINS-16813) Check permission for parametized Project name instead of requiring global read
wernight created JENKINS-16813 Check permission for parametized Project name instead of requiring global read Issue Type: Bug Assignee: Unassigned Components: copyartifact Created: 14/Feb/13 4:28 PM Description: When archiving from a dynamic project name it currently requires read permission on that project for all authenticated. In a corporate environments it means anyone in the corporation should be able to see that project. The goal would be to check that the current user has read access on the dynamically generated project. Currently without that security, we could use this plugin and make it safe in our configuration (we don't have per-project access rights). Project: Jenkins Priority: Major Reporter: wernight This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16430) Cannot connect a slave without Connect right
wernight created JENKINS-16430 Cannot connect a slave without Connect right Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ldap Created: 21/Jan/13 2:55 PM Description: Since latest LDAP and Jenkins 1.480.2 in order for slave to connect with LDAP plugin I had to give the following rights: Anonymous: Overall Read, and Slave Connect. Without those, the JNLP gives a 403 (or 404) error. This wasn't the case before. Project: Jenkins Priority: Major Reporter: wernight 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-12117) Flickers (mostly on Chrome)
wernight resolved JENKINS-12117 as Cannot Reproduce Flickers (mostly on Chrome) Change By: wernight (14/Jan/13 1:00 PM) 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
[JIRA] (JENKINS-12117) Flickers (mostly on Chrome)
wernight commented on JENKINS-12117 Flickers (mostly on Chrome) Seems not fickering anymore but it's difficult to tell the reason after all this time. Jenkins 1.480.1 Chrome 23 Firefox 18 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-10551) Check the parameter from upstream job to trigger a release build
wernight commented on JENKINS-10551 Check the parameter from upstream job to trigger a release build To upgrade there is the Promote plugin which does actually pretty much everything described. However a release trigger would be most welcome. A configurable trigger like the normal job trigger. 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-12966) gitTool crashes Jenkins startup
wernight commented on JENKINS-12966 gitTool crashes Jenkins startup It seems that installing the new dependency "Git Server Plugin" fixes this issue along with "FileBackedHttpGitRepository" exception. 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-15669) Include a test button
wernight created JENKINS-15669 Include a test button Issue Type: Bug Assignee: kutzi Components: jabber Created: 30/Oct/12 4:37 PM Description: Like the email a "Send Test Message" button should be there to check it works. Project: Jenkins Priority: Major Reporter: wernight 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-11664) Ability to add additional parameter on manual trigger
wernight edited a comment on JENKINS-11664 Ability to add additional parameter on manual trigger deleted 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-15654) Trigger on reason provided so as to change behavior for change-merged
wernight created JENKINS-15654 Trigger on reason provided so as to change behavior for change-merged Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger Created: 29/Oct/12 2:19 PM Description: Goal: Have the same job do deployment and staging by Promoting all successful Change-Merge triggered builds (promotion then does the deployment). Missing Feature: "Trigger on" reason is not provided as parameter. Note: There is no obvious way to distinguish a Patchset Created for a Merge to master Gerrit event. Two jobs are possible and works fine. Can also monitor the repo though and poll which then would have less GERRIT fields. Project: Jenkins Priority: Major Reporter: wernight 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-15501) Can't do Rebuild Action if Use the Validating String Parameter Plugin(2.2)
wernight commented on JENKINS-15501 Cant do Rebuild Action if Use the Validating String Parameter Plugin(2.2) Same here on Windows with Jenkins 1.487 and latest 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-15304) Drop list broken, does nothing
wernight commented on JENKINS-15304 Drop list broken, does nothing Chrome 22 fixed it after a full cache cookies reset. Strangely I had to clear those else I couldn't log in 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-15304) Drop list broken, does nothing
wernight created JENKINS-15304 Drop list broken, does nothing Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core, parameters Created: 25/Sep/12 4:21 PM Description: 1. Click a drop list 2. Select an item 3. Expecting the item to be added but does nothing except closing the drop list This is a recurring issue. Some places where it's broken: Job Configure Add Parameter Job Configure Add build step Job Configure Add post-build action Edit View Add Section (for sectioned view) Configure System Add Installer Environment: Jenkins 1.483 Java 7 Windows x64 Project: Jenkins Labels: jenkins Priority: Major Reporter: wernight 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-15304) Drop list broken, does nothing
wernight updated JENKINS-15304 Drop list broken, does nothing Change By: wernight (25/Sep/12 4:23 PM) Description: InChrome21.0(worksinFirefox): 1.Clickadroplist2.Selectanitem3.ExpectingtheitemtobeaddedbutdoesnothingexceptclosingthedroplistThisisarecurringissue.Someplaceswhereitsbroken:-JobConfigureAddParameter-JobConfigureAddbuildstep-JobConfigureAddpost-buildaction-EditViewAddSection(forsectionedview)-ConfigureSystemAddInstaller 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-15304) Drop list broken, does nothing
wernight updated JENKINS-15304 Drop list broken, does nothing Change By: wernight (25/Sep/12 4:25 PM) Description: InChrome21.0(worksinFirefox 13.0andIE9x64 ):1.Clickadroplist2.Selectanitem3.ExpectingtheitemtobeaddedbutdoesnothingexceptclosingthedroplistThisisarecurringissue.Someplaceswhereitsbroken:-JobConfigureAddParameter-JobConfigureAddbuildstep-JobConfigureAddpost-buildaction-EditViewAddSection(forsectionedview)-ConfigureSystemAddInstaller 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-15304) Drop list broken, does nothing
wernight updated JENKINS-15304 Drop list broken, does nothing Change By: wernight (25/Sep/12 4:25 PM) Environment: Client:-Chrome21.0-Windowsx64Server:- Jenkins1.483 - Java7 - Windowsx64 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-15290) Query and Trigger Gerrit Patches shows nothing
wernight created JENKINS-15290 Query and Trigger Gerrit Patches shows nothing Issue Type: Bug Assignee: rsandell Components: gerrit-trigger Created: 24/Sep/12 3:48 PM Description: "Query and Trigger Gerrit Patches" for "is:open" now displays nothing. Restarting Jenkins and Gerrit but still nothing. However the triggers work properly. The access right should not have changed. The only thing that changed is the SSH public hash ID which has been updated in Jenkins and works everywhere else. Upgraded to Gerrit 2.5, still same issue. Project: Jenkins Priority: Major Reporter: wernight 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-15247) Windows Slave ERROR: Message not found for errorCode: 0x00001031
wernight
created JENKINS-15247
Windows Slave ERROR: Message not found for errorCode: 0x1031
Issue Type:
Bug
Assignee:
Unassigned
Components:
master-slave
Created:
20/Sep/12 10:48 AM
Description:
After trying everything on the Wiki page and on some related issue like changing the {76A64158-CB41-11D1-8B02-00600806D9B6} key permission I still get:
ERROR: Message not found for errorCode: 0x1031
org.jinterop.dcom.common.JIException: Message not found for errorCode: 0x1031
at org.jinterop.winreg.smb.JIWinRegStub.winreg_OpenHKCR(JIWinRegStub.java:123)
at org.jinterop.dcom.core.JIComServer.initialise(JIComServer.java:479)
at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:427)
at org.jvnet.hudson.wmi.WMI.connect(WMI.java:59)
at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:219)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200)
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 java.lang.Thread.run(Unknown Source)
Caused by: java.net.MalformedURLException: For input string: "ertert0%2B@10.101.75.39"
at java.net.URL.init(Unknown Source)
at jcifs.smb.SmbFile.init(SmbFile.java:444)
at jcifs.smb.SmbNamedPipe.init(SmbNamedPipe.java:134)
at rpc.ncacn_np.RpcTransport.attach(RpcTransport.java:89)
at rpc.Stub.attach(Stub.java:104)
at rpc.Stub.call(Stub.java:109)
at org.jinterop.winreg.smb.JIWinRegStub.winreg_OpenHKCR(JIWinRegStub.java:119)
... 10 more
Environment:
Windows
Project:
Jenkins
Priority:
Major
Reporter:
wernight
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-15247) Windows Slave ERROR: Message not found for errorCode: 0x00001031
wernight commented on JENKINS-15247 Windows Slave ERROR: Message not found for errorCode: 0x1031 Solved by using username in the standard form: COMPUTERNAME\UserName instead of UserName@COMPUTERNAME 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-15247) Windows Slave ERROR: Message not found for errorCode: 0x00001031
wernight resolved JENKINS-15247 as Fixed Windows Slave ERROR: Message not found for errorCode: 0x1031 Change By: wernight (20/Sep/12 10:54 AM) 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-15230) Properties need some help
wernight
created JENKINS-15230
Properties need some help
Issue Type:
Bug
Assignee:
vjuranek
Components:
groovy
Created:
19/Sep/12 9:18 AM
Description:
Properties section help should tell how to access properties, via
System.getProperty('FOO')
Also it should tell if there are reasons not to use them to parse parameters.
Last but not least, environment variable expansion doesn't work in that field:
FOO=$WORKSPACE
Didn't get expanded.
Project:
Jenkins
Priority:
Minor
Reporter:
wernight
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-15230) Properties need some help
wernight
updated JENKINS-15230
Properties need some help
Change By:
wernight
(19/Sep/12 9:21 AM)
Description:
Propertiessectionhelpshouldtellhowtoaccessproperties,via{code}System.getProperty(FOO){code}Alsoitshouldtelliftherearereasonsnottousethemtoparseparameters.Lastbutnotleast,
some
environmentvariableexpansion
doesn
don
tworkinthatfield:{code}FOO=$WORKSPACE{code}Didntgetexpanded
whilstitworkedviatheScriptparameterssection
.
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-15216) Rename tab to Console Output [parsed]
wernight created JENKINS-15216 Rename tab to Console Output [parsed] Issue Type: Bug Assignee: rgoren Components: log-parser Created: 18/Sep/12 11:26 AM Description: The current name "Parsed Console Output" and the current icon make it harder to locate the parsed output. Ideally it should be next to the normal one like: Console Output [raw] [parsed] Alternatively it would be good to have the same icon and like: Console Output [raw] Console Output (parsed) Project: Jenkins Priority: Trivial Reporter: wernight 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-14638) Update documentation links
wernight commented on JENKINS-14638 Update documentation links Thumbs up! 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-12465) java.lang.StackOverflowError, probably in analysis of dry results?
wernight commented on JENKINS-12465 java.lang.StackOverflowError, probably in analysis of dry results? ... replaces the file path and later other lines. Sadly the generated XML would be nearly useless as the issue is a non issue if the files don't exist. 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-7079) java.net.BindException: Address already in use
wernight commented on JENKINS-7079 java.net.BindException: Address already in use Check Jenkins SSH port. This error should really display what is trying to connect and to which port number on which IP. 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-14489) Exclusion per slave
wernight commented on JENKINS-14489 Exclusion per slave I found that the Throttle Concurrent Builds Plugin does this in a lesser measure. It cannot have only a small part but it can achieve most of the desired effect. 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-14628) Fatal error on JSON parsing
wernight edited a comment on JENKINS-14628 Fatal error on JSON parsing Same issue with xUnity 1.47 and Jenkins 1.477. Downgrade to xUnit 1.46 doesn't solve and it's much harder for me to get 1.45. I'll try anyway. Shouldn't this be tagged 'xunit'? 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-14628) Fatal error on JSON parsing
wernight commented on JENKINS-14628 Fatal error on JSON parsing Same issue with xUnity 1.47 and Jenkins 1.477. Downgrade to xUnit 1.46 doesn't solve and it's much harder for me to get 1.45. I'll try anyway. 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-14628) Fatal error on JSON parsing
wernight edited a comment on JENKINS-14628 Fatal error on JSON parsing Same issue with xUnity 1.47 and Jenkins 1.477. Downgrade to xUnit 1.46 seem to fix after a full restart of Jenkins. Shouldn't this be tagged 'xunit'? 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-14714) Discard normal build parameters
wernight created JENKINS-14714 Discard normal build parameters Issue Type: Bug Assignee: Peter Hayes Components: release Created: 07/Aug/12 5:03 PM Description: For Release builds we have one parameter less. That parameter gets filled via EnvInject. For that two things would be useful: Option to completely discard default parameters and only use those given to the Release build. Make Release define a parameter so that EnvInject and other elements can differentiate release builds from other builds. Project: Jenkins Priority: Major Reporter: wernight 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-14638) Update documentation links
wernight created JENKINS-14638 Update documentation links Issue Type: Bug Assignee: wolfs Components: groovy-postbuild Created: 31/Jul/12 12:02 PM Description: The current help is very good but seems outdated. It links to HUDSON's page when it probably should link to Jenkins' page (at least because on Jenkin's page the links to the API are working). At the same time, a link to the API for "hudson", "build", and "listener" directly in that help documentation would be welcome. Project: Jenkins Priority: Trivial Reporter: wernight 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-12465) java.lang.StackOverflowError, probably in analysis of dry results?
wernight edited a comment on JENKINS-12465 java.lang.StackOverflowError, probably in analysis of dry results? Got the same issue from a Simian generated XML file. What I noticed it that the issue comes from a single element: simian version="2.3.33" check failOnDuplication="true" ignoreCharacterCase="true" ignoreCurlyBraces="true" ignoreIdentifierCase="true" ignoreModifiers="true" ignoreStringCase="true" threshold="6" set lineCount="6" block sourceFile="..." startLineNumber="8" endLineNumber="29"/ ... over 300 blocks here ... block sourceFile="..." startLineNumber="8" endLineNumber="29"/ /set summary duplicateFileCount="2043" duplicateLineCount="88608" duplicateBlockCount="7312" totalFileCount="7194" totalRawLineCount="1167701" totalSignificantLineCount="477153" processingTime="7750"/ /check /simian 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-12465) java.lang.StackOverflowError, probably in analysis of dry results?
wernight edited a comment on JENKINS-12465 java.lang.StackOverflowError, probably in analysis of dry results? Got the same issue from a Simian generated XML file. What I noticed it that the issue comes from a single element: simian version="2.3.33" check failOnDuplication="true" ignoreCharacterCase="true" ignoreCurlyBraces="true" ignoreIdentifierCase="true" ignoreModifiers="true" ignoreStringCase="true" threshold="6" set lineCount="6" block sourceFile="..." startLineNumber="8" endLineNumber="29"/ ... over 300 blocks here ... block sourceFile="..." startLineNumber="8" endLineNumber="29"/ /set summary duplicateFileCount="2043" duplicateLineCount="88608" duplicateBlockCount="7312" totalFileCount="7194" totalRawLineCount="1167701" totalSignificantLineCount="477153" processingTime="7750"/ /check /simian PS: It seems that the issue is reproducible only if the files exist. 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-12465) java.lang.StackOverflowError, probably in analysis of dry results?
wernight commented on JENKINS-12465 java.lang.StackOverflowError, probably in analysis of dry results? Got the same issue from a Simian generated XML 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-14677) Parametized build default values from URL
wernight created JENKINS-14677 Parametized build default values from URL Issue Type: Improvement Assignee: Unassigned Components: parameters Created: 03/Aug/12 10:30 AM Description: http://example.com/job/Foo/build?PARAMETER_NAME=SomeValue Should set the value default for 'PARAMETER_NAME' parameter but still ask the user to input other parameters. So 'build' URL should work like 'buildWithParameters' URL except it doesn't start immediately but asks for parameters. Project: Jenkins Priority: Minor Reporter: wernight 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-13422) Release button column
wernight updated JENKINS-13422 Release button column Mock Change By: wernight (23/Jul/12 12:28 PM) Attachment: ReleaseButton.png 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-14505) Delete button broken (and many more)
wernight updated JENKINS-14505 Delete button broken (and many more) Change By: wernight (20/Jul/12 9:23 AM) Description: Manyissuesincluding:-Deletebuttonnowworkingwheneditingalistview-Droplistsnotloadingproperlyofsomeplugins-DeleteColumnbuttonnotworkingforsectionedviewplugin-DeletebuildstepnotworkingSeealso:-http://jenkins.361315.n4.nabble.com/hetero-list-quot-delete-button-quot-doesn-t-work-for-our-plugin-in-new-Jenkins-version-td4634675.html-Possiblybrokenbyhttps://github.com/albgra/jenkins/commit/581b8256b10e1e74f9ec872664ae837c625a1d17 ThesameissuehappenonaWindowsandaLinuxJenkins.Bothrunthe1.474buthaveverydifferentsetups.Downgradingto1.473solvestheissue. 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-14505) Delete button broken (and many more)
wernight updated JENKINS-14505 Delete button broken (and many more) Change By: wernight (20/Jul/12 9:24 AM) Description: Manyissuesincluding:-Deletebuttonnowworkingwheneditingalistview-Droplistsnotloadingproperlyofsomeplugins-DeleteColumnbuttonnotworkingforsectionedviewplugin-Deletebuildstepnotworking -Manydroplistscannotadditems(whenconfiguringajobliketheReleaseplugin) Seealso:-http://jenkins.361315.n4.nabble.com/hetero-list-quot-delete-button-quot-doesn-t-work-for-our-plugin-in-new-Jenkins-version-td4634675.html-Possiblybrokenbyhttps://github.com/albgra/jenkins/commit/581b8256b10e1e74f9ec872664ae837c625a1d17ThesameissuehappenonaWindowsandaLinuxJenkins.Bothrunthe1.474buthaveverydifferentsetups.Downgradingto1.473solvestheissue. 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-14505) Delete button broken (and many more)
wernight created JENKINS-14505 Delete button broken (and many more) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core, ui-changes Created: 19/Jul/12 2:12 PM Description: Many issues including: Delete button now working when editing a list view Drop lists not loading properly of some plugins Delete Column button not working for sectioned view plugin Delete build step not working See also: http://jenkins.361315.n4.nabble.com/hetero-list-quot-delete-button-quot-doesn-t-work-for-our-plugin-in-new-Jenkins-version-td4634675.html Possibly broken by https://github.com/albgra/jenkins/commit/581b8256b10e1e74f9ec872664ae837c625a1d17 Environment: Jenkins 1.474 Project: Jenkins Priority: Critical Reporter: wernight 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-14479) Wiki documentation
wernight created JENKINS-14479 Wiki documentation Issue Type: Task Assignee: rsandell Components: gerrit-trigger Created: 18/Jul/12 9:17 AM Description: Gerrit can be complex and a Wiki documentation point would be more than useful. It's nearly necessary. The introduction on Jenkins page is far from enough and community cannot really participate well on it. Some topics or FAQ on top of my mind: Can multiple jobs review the same changeset (possibly giving different answers)? What are the access rights I need to setup in Gerrit? -- Add to non-interactive, then give read right... Why doesn't the build button work? Can I disable it? -- Re-trigger I have found answer to some the hard way and could have shared it. Other answer (like the first question above) I still need to figure it out. Project: Jenkins Priority: Major Reporter: wernight 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-14479) Wiki documentation
wernight updated JENKINS-14479 Wiki documentation Change By: wernight (18/Jul/12 9:39 AM) Description: GerritcanbecomplexandaWikidocumentationpointwouldbemorethanuseful.Itsnearlynecessary.TheintroductiononJenkinspageisfarfromenoughandcommunitycannotreallyparticipatewellonit.SometopicsorFAQontopofmymind:-Canmultiplejobsreviewthesamechangeset(possiblygivingdifferentanswers)?-WhataretheaccessrightsIneedtosetupinGerrit?--Addtonon-interactive,thengivereadright...-Whydoesntthebuildbuttonwork?CanIdisableit?--Re-triggerIhavefoundanswertosomethehardwayandcouldhavesharedit.Otheranswer(likethefirstquestionabove)Istillneedtofigureitout. Hereisagoodreferencepointtoinclude:http://strongspace.com/rtyler/public/gerrit-jenkins-notes.pdf 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-14479) Wiki documentation
wernight updated JENKINS-14479 Wiki documentation Change By: wernight (18/Jul/12 9:44 AM) Description: GerritcanbecomplexandaWikidocumentationpointwouldbemorethanuseful.Itsnearlynecessary.TheintroductiononJenkinspageisfarfromenoughandcommunitycannotreallyparticipatewellonit.SometopicsorFAQontopofmymind:-Canmultiplejobsreviewthesamechangeset(possiblygivingdifferentanswers)? --yes,seearound90%ofthePDFbelowbutshouldbeelaborated -WhataretheaccessrightsIneedtosetupinGerrit?--Addtonon-interactive,thengivereadright...-Whydoesntthebuildbuttonwork?CanIdisableit?--Re-trigger -Howtohavethebuildbuttontobuildfromabranchbydefault? Ihavefoundanswertosomethehardwayandcouldhavesharedit. Otheranswer(likethefirstquestionabove)Istillneedtofigureitout. Hereisagoodreferencepointtoinclude:http://strongspace.com/rtyler/public/gerrit-jenkins-notes.pdf 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-14445) Recording NUnit tests results very slow
wernight commented on JENKINS-14445 Recording NUnit tests results very slow It's 277 KB. We have like 100 or 200 unit tests but some of a few them may have like 500 tests cases (like those using Random). After that there is the Violation plugin which doesn't seem to log anything in the console (strangely), and Archiving artifacts which is the next I used. I'll try putting NUnit last to check if it comes from Violations. 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-14479) Wiki documentation
wernight commented on JENKINS-14479 Wiki documentation Just saw I can edit the Jenkins wiki page. I may do that. 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-14479) Wiki documentation
wernight resolved JENKINS-14479 as Fixed Wiki documentation Change By: wernight (18/Jul/12 1:24 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-14479) Wiki documentation
wernight stopped work on JENKINS-14479 Wiki documentation Change By: wernight (18/Jul/12 1:24 PM) Status: InProgress Open 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-14479) Wiki documentation
wernight assigned JENKINS-14479 to wernight Wiki documentation Change By: wernight (18/Jul/12 1:24 PM) Assignee: rsandell wernight 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-14486) Provide help icon for common settings
wernight created JENKINS-14486 Provide help icon for common settings Issue Type: Task Assignee: Nicolas De Loof Components: git Created: 18/Jul/12 1:40 PM Description: Two settings should have a help message to describe what they do: "Clean after checkout": Does a git clean -xdf globally and on each submodule? "Wipe out workspace before build" All other settings should also have some help but they are probably less frequently used. Project: Jenkins Priority: Major Reporter: wernight 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-14445) Recording NUnit tests results very slow
wernight commented on JENKINS-14445 Recording NUnit tests results very slow Now that's very particular, after moving Violations just before NUnit I don't even see those 5 min wasted anywhere. NUnit takes only a few seconds which is perfectly fine. Thank you for you help. 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-14445) Recording NUnit tests results very slow
wernight resolved JENKINS-14445 as Not A Defect Recording NUnit tests results very slow Change By: wernight (18/Jul/12 4:11 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-14489) Exclusion per slave
wernight created JENKINS-14489 Exclusion per slave Issue Type: Task Assignee: Unassigned Components: exclusion Created: 18/Jul/12 4:13 PM Description: Nearly all my exclusions are because jobs use a resource shared on that machine but not between machines. So I actually need an exclusion for each slave to avoid the same slave to run the critical block, but two different slave should be allowed to run the critical block. Project: Jenkins Priority: Major Reporter: wernight 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-14445) Recording NUnit tests results very slow
wernight created JENKINS-14445 Recording NUnit tests results very slow Issue Type: Improvement Assignee: redsolo Components: nunit Created: 16/Jul/12 5:02 PM Description: The step "Recording NUnit tests results" takes 5 minutes of our build time (a less than 30 minutes build from clean checkout including those 5 minutes). Is there something special going on that suggests this time? Project: Jenkins Priority: Major Reporter: wernight 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-13422) Release button column
[ https://issues.jenkins-ci.org/browse/JENKINS-13422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wernight updated JENKINS-13422: --- Description: Like the existing build button column, a Build Release custom column would be nice. It just would show a build button like the release one. This would allow quickly making a release. I'm talking of course about a custom column that can be used in any Jenkins view. (was: Like the existing build button column, a Build Release custom column would be nice. It just would show a build button like the release one. This would allow quickly making a release.) Release button column - Key: JENKINS-13422 URL: https://issues.jenkins-ci.org/browse/JENKINS-13422 Project: Jenkins Issue Type: New Feature Components: release Reporter: wernight Assignee: Peter Hayes Like the existing build button column, a Build Release custom column would be nice. It just would show a build button like the release one. This would allow quickly making a release. I'm talking of course about a custom column that can be used in any Jenkins view. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13422) Release button column
wernight created JENKINS-13422: -- Summary: Release button column Key: JENKINS-13422 URL: https://issues.jenkins-ci.org/browse/JENKINS-13422 Project: Jenkins Issue Type: New Feature Components: release Reporter: wernight Assignee: Peter Hayes Like the existing build button column, a Build Release custom column would be nice. It just would show a build button like the release one. This would allow quickly making a release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13385) Jenkins stop working after upgrade
wernight created JENKINS-13385: -- Summary: Jenkins stop working after upgrade Key: JENKINS-13385 URL: https://issues.jenkins-ci.org/browse/JENKINS-13385 Project: Jenkins Issue Type: Bug Components: git Reporter: wernight Assignee: Nicolas De Loof Priority: Blocker After upgrading Jenkins to 1.459 I got this exception which is removed as soon as I disable Git plugin: SEVERE: Failed to create Guice container from all the plugins com.google.common.collect.ComputationException: java.lang.TypeNotPresentException: Type hudson.plugins.view.dashboard.DashboardPortlet not present at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) at com.google.inject.internal.FailableCache.get(FailableCache.java:49) at com.google.inject.internal.MembersInjectorStore.get(MembersInjectorStore.java:66) at com.google.inject.internal.ConstructorInjectorStore.createConstructor(ConstructorInjectorStore.java:73) at com.google.inject.internal.ConstructorInjectorStore.access$000(ConstructorInjectorStore.java:29) at com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:36) at com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:33) at com.google.inject.internal.FailableCache$1.apply(FailableCache.java:38) at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) at com.google.inject.internal.FailableCache.get(FailableCache.java:49) at com.google.inject.internal.ConstructorInjectorStore.get(ConstructorInjectorStore.java:49) at com.google.inject.internal.ConstructorBindingImpl.initialize(ConstructorBindingImpl.java:127) at com.google.inject.internal.InjectorImpl.initializeBinding(InjectorImpl.java:506) at com.google.inject.internal.AbstractBindingProcessor$Processor$1.run(AbstractBindingProcessor.java:171) at com.google.inject.internal.ProcessedBindingData.initializeBindings(ProcessedBindingData.java:44) at com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:123) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107) at com.google.inject.Guice.createInjector(Guice.java:94) at com.google.inject.Guice.createInjector(Guice.java:71) at hudson.ExtensionFinder$GuiceFinder.init(ExtensionFinder.java:280) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at java.lang.Class.newInstance0(Class.java:372) at java.lang.Class.newInstance(Class.java:325) at net.java.sezpoz.IndexItem.instance(IndexItem.java:181) at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:616) at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:591) at hudson.ExtensionFinder._find(ExtensionFinder.java:149) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:289) at hudson.ExtensionList.load(ExtensionList.java:278) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:282) at hudson.ExtensionList.load(ExtensionList.java:278) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ExtensionList.get(ExtensionList.java:129) at hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:86) 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:616) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at
[JIRA] (JENKINS-13385) Jenkins stop working after upgrade
[ https://issues.jenkins-ci.org/browse/JENKINS-13385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wernight updated JENKINS-13385: --- Affects Version/s: current Description: After upgrading Jenkins to 1.459 I got this exception which is removed as soon as I disable Git plugin 1.1.16: SEVERE: Failed to create Guice container from all the plugins com.google.common.collect.ComputationException: java.lang.TypeNotPresentException: Type hudson.plugins.view.dashboard.DashboardPortlet not present at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) at com.google.inject.internal.FailableCache.get(FailableCache.java:49) at com.google.inject.internal.MembersInjectorStore.get(MembersInjectorStore.java:66) at com.google.inject.internal.ConstructorInjectorStore.createConstructor(ConstructorInjectorStore.java:73) at com.google.inject.internal.ConstructorInjectorStore.access$000(ConstructorInjectorStore.java:29) at com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:36) at com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:33) at com.google.inject.internal.FailableCache$1.apply(FailableCache.java:38) at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) at com.google.inject.internal.FailableCache.get(FailableCache.java:49) at com.google.inject.internal.ConstructorInjectorStore.get(ConstructorInjectorStore.java:49) at com.google.inject.internal.ConstructorBindingImpl.initialize(ConstructorBindingImpl.java:127) at com.google.inject.internal.InjectorImpl.initializeBinding(InjectorImpl.java:506) at com.google.inject.internal.AbstractBindingProcessor$Processor$1.run(AbstractBindingProcessor.java:171) at com.google.inject.internal.ProcessedBindingData.initializeBindings(ProcessedBindingData.java:44) at com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:123) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107) at com.google.inject.Guice.createInjector(Guice.java:94) at com.google.inject.Guice.createInjector(Guice.java:71) at hudson.ExtensionFinder$GuiceFinder.init(ExtensionFinder.java:280) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at java.lang.Class.newInstance0(Class.java:372) at java.lang.Class.newInstance(Class.java:325) at net.java.sezpoz.IndexItem.instance(IndexItem.java:181) at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:616) at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:591) at hudson.ExtensionFinder._find(ExtensionFinder.java:149) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:289) at hudson.ExtensionList.load(ExtensionList.java:278) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:282) at hudson.ExtensionList.load(ExtensionList.java:278) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ExtensionList.get(ExtensionList.java:129) at hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:86) 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:616) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$6.runTask(Jenkins.java:838) at
[JIRA] (JENKINS-13385) Jenkins stop working after upgrade
[ https://issues.jenkins-ci.org/browse/JENKINS-13385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161396#comment-161396 ] wernight commented on JENKINS-13385: Installing *Dashboard View* plugin seem to solve this issue. Jenkins stop working after upgrade -- Key: JENKINS-13385 URL: https://issues.jenkins-ci.org/browse/JENKINS-13385 Project: Jenkins Issue Type: Bug Components: git Affects Versions: current Reporter: wernight Assignee: Nicolas De Loof Priority: Blocker After upgrading Jenkins to 1.459 I got this exception which is removed as soon as I disable Git plugin 1.1.16: SEVERE: Failed to create Guice container from all the plugins com.google.common.collect.ComputationException: java.lang.TypeNotPresentException: Type hudson.plugins.view.dashboard.DashboardPortlet not present at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) at com.google.inject.internal.FailableCache.get(FailableCache.java:49) at com.google.inject.internal.MembersInjectorStore.get(MembersInjectorStore.java:66) at com.google.inject.internal.ConstructorInjectorStore.createConstructor(ConstructorInjectorStore.java:73) at com.google.inject.internal.ConstructorInjectorStore.access$000(ConstructorInjectorStore.java:29) at com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:36) at com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:33) at com.google.inject.internal.FailableCache$1.apply(FailableCache.java:38) at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) at com.google.inject.internal.FailableCache.get(FailableCache.java:49) at com.google.inject.internal.ConstructorInjectorStore.get(ConstructorInjectorStore.java:49) at com.google.inject.internal.ConstructorBindingImpl.initialize(ConstructorBindingImpl.java:127) at com.google.inject.internal.InjectorImpl.initializeBinding(InjectorImpl.java:506) at com.google.inject.internal.AbstractBindingProcessor$Processor$1.run(AbstractBindingProcessor.java:171) at com.google.inject.internal.ProcessedBindingData.initializeBindings(ProcessedBindingData.java:44) at com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:123) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107) at com.google.inject.Guice.createInjector(Guice.java:94) at com.google.inject.Guice.createInjector(Guice.java:71) at hudson.ExtensionFinder$GuiceFinder.init(ExtensionFinder.java:280) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at java.lang.Class.newInstance0(Class.java:372) at java.lang.Class.newInstance(Class.java:325) at net.java.sezpoz.IndexItem.instance(IndexItem.java:181) at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:616) at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:591) at hudson.ExtensionFinder._find(ExtensionFinder.java:149) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:289) at hudson.ExtensionList.load(ExtensionList.java:278) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:282) at hudson.ExtensionList.load(ExtensionList.java:278) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ExtensionList.get(ExtensionList.java:129) at hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:86) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
[JIRA] (JENKINS-13316) Configuration keeps Loading message and nothing works
wernight created JENKINS-13316: -- Summary: Configuration keeps Loading message and nothing works Key: JENKINS-13316 URL: https://issues.jenkins-ci.org/browse/JENKINS-13316 Project: Jenkins Issue Type: Bug Components: log-parser Environment: Jenkins ver. 1.457 on Windows Server Reporter: wernight Assignee: rgoren Priority: Critical Restarted Jenkins completely after installing the plugin. Jenkins global configuration page now keeps the LOADING with gray background and buttons don't work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13316) Configuration keeps Loading message and nothing works
[ https://issues.jenkins-ci.org/browse/JENKINS-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161103#comment-161103 ] wernight commented on JENKINS-13316: I've just tried disabling that plugin seem to have no effect. It might be due to the upgrade of another plugin. Configuration keeps Loading message and nothing works --- Key: JENKINS-13316 URL: https://issues.jenkins-ci.org/browse/JENKINS-13316 Project: Jenkins Issue Type: Bug Components: log-parser Environment: Jenkins ver. 1.457 on Windows Server Reporter: wernight Assignee: rgoren Priority: Critical Restarted Jenkins completely after installing the plugin. Jenkins global configuration page now keeps the LOADING with gray background and buttons don't work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13316) Configuration keeps Loading message and nothing works
[ https://issues.jenkins-ci.org/browse/JENKINS-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wernight resolved JENKINS-13316. Resolution: Not A Defect Probably due to another plugin. Completely uninstalled a bunch of plugins and now works. Configuration keeps Loading message and nothing works --- Key: JENKINS-13316 URL: https://issues.jenkins-ci.org/browse/JENKINS-13316 Project: Jenkins Issue Type: Bug Components: log-parser Environment: Jenkins ver. 1.457 on Windows Server Reporter: wernight Assignee: rgoren Priority: Critical Restarted Jenkins completely after installing the plugin. Jenkins global configuration page now keeps the LOADING with gray background and buttons don't work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10440) gerrit trigger plugin fails to run mvn command when non escaped chards are in subject
[ https://issues.jenkins-ci.org/browse/JENKINS-10440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160934#comment-160934 ] wernight commented on JENKINS-10440: This issue is still live. Maven2 is the de-facto Maven of Ubuntu 11, so there is no simple fix. Any way to remove all those extra definitions? Shouldn't they go as environment variables instead? gerrit trigger plugin fails to run mvn command when non escaped chards are in subject Key: JENKINS-10440 URL: https://issues.jenkins-ci.org/browse/JENKINS-10440 Project: Jenkins Issue Type: Bug Components: gerrit-trigger Affects Versions: current Environment: Jenkins 1.421 RedHat enterprize 6.1 x86_64 Reporter: Eyal Edri Assignee: rsandell when jenkins triggers a build using gerrit trigger plugin and the -DGERRIT_CHANGE_SUBJECT contains chars, it doesnt escapse the char properly and mvn command fails. the original patch text: adding \ to end of search will cause Exception message example run: /var/lib/jenkins/tools/maven_2.2.1/bin/mvn '-DGERRIT_CHANGE_SUBJECT=adding \\\ to end of search will cause Exception message ' -DGERRIT_REFSPEC=refs/changes/76/1076/6 -DGERRIT_BRANCH=review -DGERRIT_PATCHSET_NUMBER=6 -DGERRIT_CHANGE_URL=http://gerrit.server.com/1076 -DGERRIT_CHANGE_ID=Ied1bcb88901485a62a4ec236edd7d10816edf9ba -DGERRIT_PATCHSET_REVISION=226c6b02b5a12f0cfa2af1c9d9f634c1cf928184 -DGERRIT_CHANGE_NUMBER=1076 -DGERRIT_PROJECT=rhevm -Dmaven.repo.local=/mnt/iscsi/workspaces/gerrit_tests/.repository clean install findbugs:findbugs maven fails with: [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Invalid task 'to': you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Sun Jul 24 23:42:17 IDT 2011 [INFO] Final Memory: 45M/7850M [INFO] Build step 'Invoke top-level Maven targets' marked build as failure ERROR: Publisher hudson.plugins.findbugs.FindBugsPublisher aborted due to exception java.lang.InterruptedException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:485) at hudson.model.Run$Runner$CheckpointSet.waitForCheckPoint(Run.java:1267) at hudson.model.Run.waitForCheckpoint(Run.java:1235) at hudson.model.CheckPoint.block(CheckPoint.java:144) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:25) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:682) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:657) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:635) at hudson.model.Build$RunnerImpl.post2(Build.java:161) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:604) at hudson.model.Run.run(Run.java:1400) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:175) Finished: FAILURE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8227) queue: job information extension
[
https://issues.jenkins-ci.org/browse/JENKINS-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160533#comment-160533
]
wernight commented on JENKINS-8227:
---
Same here. We have some very long jobs and we'd like to know who queued some
jobs and with which parameters.
queue: job information extension
Key: JENKINS-8227
URL: https://issues.jenkins-ci.org/browse/JENKINS-8227
Project: Jenkins
Issue Type: Improvement
Components: core
Environment: Hudson 1.382
Reporter: krulls
Priority: Trivial
This is a suggestion to extend the information tooltip in the queue.jelly:
As we have a lot of jobs that are building regularly from time schedule our
hudson queue has a lot of items. People wanted to know which of these
scheduled jobs were caused by a user action to potentially abort
automatically scheduled builds. So I modified the _queue.jelly_ file in the
core.jar under _lib/hudson_
Maybe this would be a feature for other customers too? Here are the
modifications (relate to hudson 1.382) surrounded by comments:
{code:title=queue.jelly}
...
j:otherwise
j:forEach var=item items=${items}
tr
!-- MOD info causes --
j:set var=allCausesText
Trigger Causes:/j:set
j:set var=userCause value=${false} /
j:forEach var=ca items=${item.causes}
j:set var=allCausesText${allCausesText}
- ${ca.shortDescription}
/j:set
j:if test=${ca.class.name.contains('UserCause')}
j:set var=userCause value=${true} /
/j:if
/j:forEach
j:set var=allCausesText${allCausesText}
/j:set
j:set var=paneTooltip
value=${item.why}${h.escape(allCausesText)}${h.escape(item.params)} /
!-- END MOD info causes --
td class=pane width=100% tooltip=${paneTooltip}
style=white-space: normal;
j:set var=stuck value=${item.isStuck()}/
j:choose
j:when test=${h.hasPermission(item.task,item.task.READ)}
a
href=${rootURL}/${item.task.url}${item.task.fullDisplayName}/a
!-- MOD manual build --
j:if test=${userCause}
#160;
img src=${imagesURL}/16x16/person.gif /
/j:if
!-- END MOD manual build --
j:if test=${stuck}
#160;
...
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8227) queue: job information extension
[
https://issues.jenkins-ci.org/browse/JENKINS-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160560#comment-160560
]
wernight commented on JENKINS-8227:
---
As a temporary workaround, you can open http://my.jenkins.host/queue/api/xml
which will display the details of all queued jobs.
queue: job information extension
Key: JENKINS-8227
URL: https://issues.jenkins-ci.org/browse/JENKINS-8227
Project: Jenkins
Issue Type: Improvement
Components: core
Environment: Hudson 1.382
Reporter: krulls
Priority: Trivial
This is a suggestion to extend the information tooltip in the queue.jelly:
As we have a lot of jobs that are building regularly from time schedule our
hudson queue has a lot of items. People wanted to know which of these
scheduled jobs were caused by a user action to potentially abort
automatically scheduled builds. So I modified the _queue.jelly_ file in the
core.jar under _lib/hudson_
Maybe this would be a feature for other customers too? Here are the
modifications (relate to hudson 1.382) surrounded by comments:
{code:title=queue.jelly}
...
j:otherwise
j:forEach var=item items=${items}
tr
!-- MOD info causes --
j:set var=allCausesText
Trigger Causes:/j:set
j:set var=userCause value=${false} /
j:forEach var=ca items=${item.causes}
j:set var=allCausesText${allCausesText}
- ${ca.shortDescription}
/j:set
j:if test=${ca.class.name.contains('UserCause')}
j:set var=userCause value=${true} /
/j:if
/j:forEach
j:set var=allCausesText${allCausesText}
/j:set
j:set var=paneTooltip
value=${item.why}${h.escape(allCausesText)}${h.escape(item.params)} /
!-- END MOD info causes --
td class=pane width=100% tooltip=${paneTooltip}
style=white-space: normal;
j:set var=stuck value=${item.isStuck()}/
j:choose
j:when test=${h.hasPermission(item.task,item.task.READ)}
a
href=${rootURL}/${item.task.url}${item.task.fullDisplayName}/a
!-- MOD manual build --
j:if test=${userCause}
#160;
img src=${imagesURL}/16x16/person.gif /
/j:if
!-- END MOD manual build --
j:if test=${stuck}
#160;
...
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
