[JIRA] (JENKINS-12259) NullPointerException in maven-plugin: Maven3Builder / ExecutedMojo (1.445)
hagzag commented on JENKINS-12259 NullPointerException in maven-plugin: Maven3Builder / ExecutedMojo (1.445) I have the same exact issue with 1.496 (I validated the maven integration plugin isn't pinned): Waiting for Jenkins to finish collecting data mavenExecutionResult exceptions not empty message : Internal error: java.lang.NullPointerException cause : null Stack trace : org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.NullPointerException at hudson.maven.Maven3Builder$MavenExecutionListener.recordProjectStarted(Maven3Builder.java:329) at hudson.maven.Maven3Builder$MavenExecutionListener.projectStarted(Maven3Builder.java:319) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:71) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:78) ... 24 more channel stopped Notifying upstream projects of job completion Finished: FAILURE 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-12259) NullPointerException in maven-plugin: Maven3Builder / ExecutedMojo (1.445)
hagzag reopened JENKINS-12259 NullPointerException in maven-plugin: Maven3Builder / ExecutedMojo (1.445) Still happening in 1.496, more info :: https://issues.jenkins-ci.org/browse/JENKINS-12259?focusedCommentId=171441page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-171441 Change By: hagzag (02/Jan/13 8:22 AM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16235) When running sudo command it gives error sudo: no tty present and no askpass program specified
harish Kayarohanam created JENKINS-16235 When running sudo command it gives error sudo: no tty present and no askpass program specified Issue Type: Bug Assignee: Unassigned Attachments: error-running-sudo.png Components: ssh Created: 02/Jan/13 9:22 AM Description: When I run sudo command ,it throws error which reads "sudo: no tty present and no askpass program specified " .Is there not any way that you get password from user and use that to run sudo commands even .? Environment: linux Project: Jenkins Labels: plugin Priority: Major Reporter: harish Kayarohanam 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-16236) window.webkitNotifications.createHTMLNotification() is deprecated/removed from Chrome
Jørgen Jervidalo created JENKINS-16236 window.webkitNotifications.createHTMLNotification() is deprecated/removed from Chrome Issue Type: Bug Assignee: jieryn Components: html5-notifier Created: 02/Jan/13 9:33 AM Description: See https://plus.google.com/u/0/+GoogleChromeDevelopers/posts/8vWo8hq4pDm window.webkitNotifications.createNotification() still works. Project: Jenkins Priority: Major Reporter: Jørgen Jervidalo 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-11574) Player was penalized for maven release.
Dominique Jean-Prost commented on JENKINS-11574 Player was penalized for maven release. Same problem for me. I installed the maven release plugin. Each time I release a component through this plugin, although the release runs well, and that all tests are run, I get this problem : it wrongly detects removed tests. Do you need more info to work on this ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16237) Extended email plugin no longer sends messages on latest
Jamie Penman-Smithson created JENKINS-16237 Extended email plugin no longer sends messages on latest Issue Type: Bug Affects Versions: current Assignee: Slide-O-Mix Components: email-ext Created: 02/Jan/13 12:25 PM Description: The email-ext plugin no longer sends messages, instead it hangs after sending DATA: 10:47:33 Checking for post-build 10:47:33 Performing post-build step 10:47:33 Checking if email needs to be generated 10:47:33 Email was triggered for: Success 10:47:33 Sending email for trigger: Success 10:47:33 NOT overriding default server settings, using Mailer to create session 10:47:33 Changing BUILD_ID variable (job build time) with the date pattern MMdd. 10:47:33 Changing BUILD_ID variable (job build time) with the date pattern MMdd. 10:47:33 messageContentType = text/plain; charset=UTF-8 10:47:33 Changing BUILD_ID variable (job build time) with the date pattern MMdd. 10:47:33 Adding developers 10:47:33 Sending to requester 10:47:33 Changing BUILD_ID variable (job build time) with the date pattern MMdd. 10:47:33 Successfully created MimeMessage 10:47:33 Sending email to: jamie.penman-smith...@example.com 10:48:34 ERROR: Could not send email as a part of the post-build publishers. 10:48:34 javax.mail.MessagingException: Exception reading response; 10:48:34 nested exception is: 10:48:34 java.net.SocketTimeoutException: Read timed out 10:48:34 at com.sun.mail.smtp.SMTPTransport.readServerResponse(SMTPTransport.java:2153) 10:48:34 at com.sun.mail.smtp.SMTPTransport.close(SMTPTransport.java:1186) 10:48:34 at javax.mail.Transport.send0(Transport.java:197) 10:48:34 at javax.mail.Transport.send(Transport.java:124) 10:48:34 at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:308) 10:48:34 at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:289) 10:48:34 at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:249) 10:48:34 at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) 10:48:34 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) 10:48:34 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:779) 10:48:34 at hudson.ivy.IvyModuleSetBuild$RunnerImpl.cleanUp(IvyModuleSetBuild.java:606) 10:48:34 at hudson.model.Run.execute(Run.java:1587) 10:48:34 at hudson.model.Run.run(Run.java:1489) 10:48:34 at hudson.ivy.IvyModuleSetBuild.run(IvyModuleSetBuild.java:282) 10:48:34 at hudson.model.ResourceController.execute(ResourceController.java:88) 10:48:34 at hudson.model.Executor.run(Executor.java:236) 10:48:34 Caused by: java.net.SocketTimeoutException: Read timed out 10:48:34 at java.net.SocketInputStream.socketRead0(Native Method) 10:48:34 at java.net.SocketInputStream.read(SocketInputStream.java:129) 10:48:34 at com.sun.mail.util.TraceInputStream.read(TraceInputStream.java:110) 10:48:34 at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) 10:48:34 at java.io.BufferedInputStream.read(BufferedInputStream.java:237) 10:48:34 at com.sun.mail.util.LineInputStream.readLine(LineInputStream.java:89) 10:48:34 at com.sun.mail.smtp.SMTPTransport.readServerResponse(SMTPTransport.java:2131) 10:48:34 ... 15 more 10:48:34 Some error occured trying to send the email...check the Jenkins log 10:48:34 Finished: SUCCESS Looking at the Postfix log in debug mode, I can see that it sends MAIL FROM and RCPT TO correctly, but after it sends DATA it does not send anything else. Eventually the connection times out and the exception above is reported in the log. The standard email functionality continues to work as normal. From postfix it only shows that it received 'DATA' but nothing more: Jan 2 12:07:59 ukfd-ecat postfix/smtpd32091: ukfd-ecat192.168.117.125: 220 ukfd-ecat.eu.example.com ESMTP Postfix Jan 2 12:07:59 ukfd-ecat postfix/smtpd32091: ukfd-ecat192.168.117.125: EHLO ukfd-ecat Jan 2 12:07:59 ukfd-ecat postfix/smtpd32091:
[JIRA] (JENKINS-16237) Extended email plugin no longer sends messages on latest
Slide-O-Mix commented on JENKINS-16237 Extended email plugin no longer sends messages on latest The plugin will not work with latest, this is a known issue because of breaking changes in core. Email-ext is not and will not be tested against anything but the latest LTS release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16237) Extended email plugin no longer sends messages on latest
Slide-O-Mix commented on JENKINS-16237 Extended email plugin no longer sends messages on latest As a workaround, you can try overriding the default settings for the mail server info in the global config. 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-16238) SimpleThemePluggin : logo jenkins.png loaded after css file
seb uz created JENKINS-16238 SimpleThemePluggin : logo jenkins.png loaded after css file Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: gui Created: 02/Jan/13 12:54 PM Description: When using Simple Theme Pluggin, it's no more possible to change the main jenkins logo (botom left). Indeed, the logo is loaded with css directly in the html declaration. Not working : index.html table id="main-table" height="70%" style="background-image: url(/jenkins/static/f7d903ac/images/jenkins.png);background-repeat: no-repeat; background-position: bottom left;" Should be : index.html table id="main-table" height="70%" and in css/style.css #main-table{ background-image: url(/jenkins/static/f7d903ac/images/jenkins.png); background-repeat: no-repeat } Project: Jenkins Labels: plugin css simplethemepluggin logo Priority: Trivial Reporter: seb uz 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-16237) Extended email plugin no longer sends messages on latest
Jamie Penman-Smithson commented on JENKINS-16237 Extended email plugin no longer sends messages on latest I've downgraded to the latest LTS release (1.480.1) and it still hangs at the same point. I've also overridden the global settings and it does the same thing: Overriding default server settings, creating our own session messageContentType = text/plain; charset=UTF-8 Changing BUILD_ID variable (job build time) with the date pattern MMdd. Adding recipients from recipient list Adding developers Sending to requester Successfully created MimeMessage Sending email to: eubu...@example.com jamie.penman-smith...@example.com Thanks, Jamie 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-15963) EnvInject properties not consistently used for SCM
Trevor Baker commented on JENKINS-15963 EnvInject properties not consistently used for SCM What is meant by "previous environment variables"? 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-16237) Extended email plugin no longer sends messages on latest
Slide-O-Mix commented on JENKINS-16237 Extended email plugin no longer sends messages on latest I am unable to reproduce this issue with the LTS. 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-16239) NPE in getRootDir
Krzysztof Malinowski created JENKINS-16239 NPE in getRootDir Issue Type: Bug Assignee: Gregory Boissinot Components: core, envinject Created: 02/Jan/13 1:50 PM Description: Upon startup projects are being loaded and for some (matrix) projects the log contains: java.lang.NullPointerException at hudson.model.Run.getRootDir(Run.java:927) at org.jenkinsci.lib.envinject.EnvInjectAction.readResolve(EnvInjectAction.java:86) Environment: Jenkins 1.496 on RHEL5 x86_64, EnvInject 1.78 Project: Jenkins Priority: Major Reporter: Krzysztof Malinowski 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-16240) Problem with NOT_BUILT build result
ThiagoC created JENKINS-16240 Problem with NOT_BUILT build result Issue Type: Bug Assignee: bap Attachments: jenkins-not_built-build-console.PNG, jenkins-not_built-module-console.PNG, jenkins-not_built-modules.PNG Components: publish-over-ssh Created: 02/Jan/13 2:30 PM Description: I'm having a problem that sometimes when a multi-module project is built and one or more modules have NOT_BUILT as result, the Publish Over SSH Plugin prints this in the console: [INFO] [INFO] BUILD SUCCESSFUL [INFO] ... channel stopped ... [EnvInject] - Injecting environment variables from a build step. ... [EnvInject] - Variables injected successfully. [EnvInject] - Unset unresolved 'BUILD_USER_LAST_NAME' variable. [EnvInject] - Unset unresolved 'NODE_NAME' variable. SSH: Current build result is [NOT_BUILT], not going to run. [M2Release] marking build to keep until the next release build Despite the fact that the total build result is SUCCESS: Finished: SUCCESS I suggest that the plugin should check the build result of the complete build without checking the result of the modules. Environment: Jenkins 1.466 Publish Over SSH Plugin 1.8 EnvInject Plugin 1.70 Jenkins Maven Release Plug-in Plug-in 0.9.1 Multi-module Maven Project Project: Jenkins Priority: Major Reporter: ThiagoC 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-16240) Problem with NOT_BUILT build result
ThiagoC updated JENKINS-16240 Problem with NOT_BUILT build result Change By: ThiagoC (02/Jan/13 2:30 PM) Assignee: bap 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-8312) svn:externals not being checked out
Juan Alvarez commented on JENKINS-8312 svn:externals not being checked out This worked for me: go to jenkins_server/scm/SubversionSCM/enterCredential and put the credentials for the external repository there. Then I deleted the repository and launch the build again (I don't know if it works for an update operation). Hope this helps! Juan M. 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-16241) Login doesn't ignore extra strings during login
aflat created JENKINS-16241 Login doesnt ignore extra strings during login Issue Type: Bug Affects Versions: current Assignee: Rob Petti Components: perforce Created: 02/Jan/13 3:48 PM Description: perforce plugin: 1.3.18 jenkins: 1.484 I use AD for authentication, so I have my own authentication script on the perforce server. A "p4 login -a -p" prints Success: Password Verified. THE_TOKEN_FROM_PERFORCE As of 1.3.18 the plugin tries to use "p4 -P "Success: Password verified." workspace -o " instead of using THE_TOKEN_FROM_PERFORCE I can change my authentication script to not print this on my server, but I also have to use another perforce server that I'm not in control of, they print other things, so I'm not sure I can get them to change that. Prior versions of this plugin didn't have this issue. Environment: Windows master and slave Project: Jenkins Priority: Major Reporter: aflat 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-16241) Login doesn't ignore extra strings during login
Rob Petti resolved JENKINS-16241 as Duplicate Login doesnt ignore extra strings during login Change By: Rob Petti (02/Jan/13 3:56 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16181) Jenkins does not try to resend a failed e-mail
Slide-O-Mix commented on JENKINS-16181 Jenkins does not try to resend a failed e-mail I don't think a queuing mechanism would be a good idea. I'll look into retries for specific issues (socket exceptions, etc). 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-15994) Perforce session ticket is not parsed correctly (again)
SCM/JIRA link daemon resolved JENKINS-15994 as Fixed Perforce session ticket is not parsed correctly (again) Change By: SCM/JIRA link daemon (02/Jan/13 4:10 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-15994) Perforce session ticket is not parsed correctly (again)
SCM/JIRA link daemon commented on JENKINS-15994 Perforce session ticket is not parsed correctly (again) Code changed in jenkins User: Rob Petti Path: src/main/java/com/tek42/perforce/parse/AbstractPerforceTemplate.java http://jenkins-ci.org/commit/perforce-plugin/7c747801ad7952ba011226af12a3c6513f96cd17 Log: FIXED JENKINS-15994 get ticket parsing during login to work when there is custom authentication trigger output 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-16169) PROMOTED_* variables are not available when sending mail on a Promotion event
Slide-O-Mix resolved JENKINS-16169 as Incomplete PROMOTED_* variables are not available when sending mail on a Promotion event Change By: Slide-O-Mix (02/Jan/13 4:12 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix resolved JENKINS-16163 as Not A Defect NullPointerException when sending post build emails - all triggers appear to be impacted There were breaking changes in 1.494 and above, email-ext is only guaranteed to work with latest LTS. Change By: Slide-O-Mix (02/Jan/13 4:20 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-16242) Github pull request builder - branch to merged before build
Radek Chromy created JENKINS-16242 Github pull request builder - branch to merged before build Issue Type: Improvement Assignee: Honza Brázdil Components: github, plugin Created: 02/Jan/13 4:21 PM Description: Can the plugin be extended by merging to the branch where the pull is created to? Use Case: Assume git repository with 2 branches: master stable01 Create pull requests to merge to any of branch. Need to run build of the pull request with merge to the target branch. Project: Jenkins Labels: plugin Priority: Critical Reporter: Radek Chromy 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-15783) email-ext Groovy script does not run when machine shuts down during job
Slide-O-Mix resolved JENKINS-15783 as Incomplete email-ext Groovy script does not run when machine shuts down during job Need more information from submitter. Reopen with more information. Change By: Slide-O-Mix (02/Jan/13 4:21 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15502) Email-ext issues: attachments feature creating issues
Slide-O-Mix resolved JENKINS-15502 as Incomplete Email-ext issues: attachments feature creating issues Need more information from submitted. Reopen with more information. Change By: Slide-O-Mix (02/Jan/13 4:22 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15311) Email-ext can't recover after a failed smtp delivery
Slide-O-Mix resolved JENKINS-15311 as Incomplete Email-ext cant recover after a failed smtp delivery Need more information from submitted. Reopen with more information. Change By: Slide-O-Mix (02/Jan/13 4:22 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6922) PROJECT_URL variable not correctly set when email is sent by Promoted Build Plugin
Slide-O-Mix commented on JENKINS-6922 PROJECT_URL variable not correctly set when email is sent by Promoted Build Plugin If you made something available via the token-macro plugin, email-ext could use it, but other than that I don't have any ideas. 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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
kutzi commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted If there were changes in core which can break plugins in such a way, is there a bug reported against core already? 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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted This is because of the split of Mailer out of core. I don't know if an issue was filed against core or not. 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-16181) Jenkins does not try to resend a failed e-mail
kutzi commented on JENKINS-16181 Jenkins does not try to resend a failed e-mail IMHO Jenkins is not responsible for reliable e-mail delivery (if you want such thing, you should make your e-mail infrastructure reliable). But some - not too many! - retries probably won't hurt! But remember that this may needlessly delay the completion of jobs if the e-mail server continues to be unavailable. 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-16181) Jenkins does not try to resend a failed e-mail
Slide-O-Mix commented on JENKINS-16181 Jenkins does not try to resend a failed e-mail I agree, this is why I will restrict the number of retries to maybe even just one. 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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
kutzi commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Then maybe we should reopen this and assign this to core? The split-out of the Mailer should be transparent to all plugins relying on it. If it's not that's clearly a bug in core. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16244) View.hasPeople too slow to use in sidepanel.jelly
Jesse Glick created JENKINS-16244 View.hasPeople too slow to use in sidepanel.jelly Issue Type: Bug Assignee: Jesse Glick Components: core Created: 02/Jan/13 5:30 PM Description: On large Jenkins installations, rendering view pages can be extremely slow. Thread dumps point to the use of View.hasPeople, which is an arbitrarily expensive call that must not be made from HTTP service. Project: Jenkins Labels: performance Priority: Major Reporter: Jesse Glick 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-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted FYI, the line causing the exception is as follows: msg = new MimeMessage(Mailer.descriptor().createSession()); I am not seeing this issue when I try and run with the latest (1.496) as part of the pom. Perhaps I will try installing into a separate instance of Jenkins and seeing if I see the same issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix updated JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Change By: Slide-O-Mix (02/Jan/13 5:35 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix reopened JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Reopening and assigning to core since this was a breaking change in core. Change By: Slide-O-Mix (02/Jan/13 5:34 PM) Resolution: NotADefect Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16244) View.hasPeople too slow to use in sidepanel.jelly
Jesse Glick started work on JENKINS-16244 View.hasPeople too slow to use in sidepanel.jelly Change By: Jesse Glick (02/Jan/13 5:48 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16244) View.hasPeople too slow to use in sidepanel.jelly
Jesse Glick commented on JENKINS-16244 View.hasPeople too slow to use in sidepanel.jelly Fixing by just unconditionally linking to asynchPeople. Unclear if hyperlink construction in this sidepanel is correct in all cases; https://github.com/jenkinsci/jenkins/commit/5c7184d3cdccde44eaf8d73a38151a1c6ee5f9a9 has discussion. 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-16244) View.hasPeople too slow to use in sidepanel.jelly
Jesse Glick updated JENKINS-16244 View.hasPeople too slow to use in sidepanel.jelly Change By: Jesse Glick (02/Jan/13 5:59 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16244) View.hasPeople too slow to use in sidepanel.jelly
SCM/JIRA link daemon resolved JENKINS-16244 as Fixed View.hasPeople too slow to use in sidepanel.jelly Change By: SCM/JIRA link daemon (02/Jan/13 6:03 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16244) View.hasPeople too slow to use in sidepanel.jelly
SCM/JIRA link daemon commented on JENKINS-16244 View.hasPeople too slow to use in sidepanel.jelly Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/View.java core/src/main/java/jenkins/model/Jenkins.java core/src/main/resources/hudson/model/View/sidepanel.jelly http://jenkins-ci.org/commit/jenkins/73aac1073983e1f667d801387571d31857253ffc Log: FIXED JENKINS-16244 View.hasPeople too slow to use in sidepanel.jelly. Compare: https://github.com/jenkinsci/jenkins/compare/5eede6e5d58d...73aac1073983 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-16042) NullPointer when collecting successful results
François Dussert commented on JENKINS-16042 NullPointer when collecting successful results Hi, I just send a pull request https://github.com/jenkinsci/tikal-multijob-plugin/pull/14 It is just a fix for the NPE, not for the real problem that seems to be that success build has a null result oO But with this, success build would not fail because of NPE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-777) The need for Subversion command line options.
SCM/JIRA link daemon commented on JENKINS-777 The need for Subversion command line options. Code changed in jenkins User: Peter Ross Path: src/main/java/hudson/scm/SubversionSCM.java src/main/java/hudson/scm/subversion/CheckoutUpdater.java src/main/java/hudson/scm/subversion/UpdateUpdater.java src/main/java/hudson/scm/subversion/UpdateWithRevertUpdater.java src/main/java/hudson/scm/subversion/WorkspaceUpdater.java src/main/resources/hudson/scm/SubversionSCM/config.jelly src/main/resources/hudson/scm/SubversionSCM/help-depthOption.html src/main/resources/hudson/scm/SubversionSCM/help-ignoreExternalsOption.html src/test/java/hudson/scm/SubversionSCMTest.java src/test/resources/hudson/scm/JENKINS-777.zip http://jenkins-ci.org/commit/subversion-plugin/e591847a3d51493fe84d84cfaaa4205952e7b50b Log: JENKINS-777 Add ability to set depth and ignore externals for a svn module. This is based on the commit b2ac2f82a of the hudson subversion plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-777) The need for Subversion command line options.
SCM/JIRA link daemon commented on JENKINS-777 The need for Subversion command line options. Code changed in jenkins User: Christoph Kutzinski Path: src/main/java/hudson/scm/SubversionSCM.java src/main/java/hudson/scm/subversion/CheckoutUpdater.java src/main/java/hudson/scm/subversion/UpdateUpdater.java src/main/java/hudson/scm/subversion/UpdateWithRevertUpdater.java src/main/java/hudson/scm/subversion/WorkspaceUpdater.java src/main/resources/hudson/scm/SubversionSCM/config.jelly src/main/resources/hudson/scm/SubversionSCM/help-depthOption.html src/main/resources/hudson/scm/SubversionSCM/help-ignoreExternalsOption.html src/test/java/hudson/scm/SubversionSCMTest.java src/test/resources/hudson/scm/JENKINS-777.zip http://jenkins-ci.org/commit/subversion-plugin/4509e8b91f4edd55b01a798eff0ef1ec35a10309 Log: Merge pull request #29 from petdr/jenkins-777 FIXED JENKINS-777 Add ability to set depth and ignore externals for a module Compare: https://github.com/jenkinsci/subversion-plugin/compare/52e83ab909bc...4509e8b91f4e This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-777) The need for Subversion command line options.
SCM/JIRA link daemon resolved JENKINS-777 as Fixed The need for Subversion command line options. Change By: SCM/JIRA link daemon (02/Jan/13 7:07 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-16245) Grails plugin - cannot execute two-word command
Wojtek Erbetowski created JENKINS-16245 Grails plugin - cannot execute two-word command Issue Type: Bug Assignee: jeffg2one Components: grails Created: 02/Jan/13 7:19 PM Description: My case is to run command "grails tomcat production", but plugin seems to execute each part as separate command (it gives 'grails tomcat' command first, which breaks). Project: Jenkins Priority: Minor Reporter: Wojtek Erbetowski 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-16246) A failure of the uninstall package build step does not result in a build failure
Joris van der Pol created JENKINS-16246 A failure of the uninstall package build step does not result in a build failure Issue Type: Bug Affects Versions: current Assignee: Christopher Orr Components: android-emulator Created: 02/Jan/13 7:36 PM Description: When trying to uninstall a package , a failure to do so, does not result in a build failure. Project: Jenkins Priority: Minor Reporter: Joris van der Pol 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-15963) EnvInject properties not consistently used for SCM
Gregory Boissinot commented on JENKINS-15963 EnvInject properties not consistently used for SCM Injected environment variables from the previous build, meaning not the scheduled build. Therefore it the last build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14538) Separate configure tools page
Jesse Glick reopened JENKINS-14538 Separate configure tools page Feel free to try to resurrect the more complicated change and fix up the remaining issues. It is still there in history (8670e13 reverted it and switched to the easier patch). But now it is possible to use GlobalConfigurationCategory introduced (5218b76) for the Global Security change (https://github.com/jenkinsci/jenkins/pull/628). getSortedDescriptorsForGlobalConfigNoSecurity would need to be deprecated and replaced with something like getSortedDescriptorsForUnclassifiedGlobalConfig. Change By: Jesse Glick (02/Jan/13 8:20 PM) Resolution: Fixed Status: Resolved Reopened Assignee: domi 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-16247) Priority Sorter should use default sort order on equal priorities
dmigowski created JENKINS-16247 Priority Sorter should use default sort order on equal priorities Issue Type: Improvement Affects Versions: current Assignee: bklarson Components: prioritysorter Created: 02/Jan/13 9:07 PM Description: The class PrioritySorterQueueSorter just sorts Build jobs by their priority, while the default QueueSorter seems to order jobs in the order they are added to the queue. I believe that this order should remain when the priority is equal, because now installing the Priority Sorter plugin without actually using it is like installing a random build order plugin. The fix should be very easy. Just use the default sort order in case the priorities of two jobs (as returned from the getPriority(BuildableItem buildable)-function in PrioritySorterQueueSorter) is equal, order by the date added to the queue. I would do it for myself, but just don't have a build environment set up for this. Environment: any Project: Jenkins Priority: Major Reporter: dmigowski 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-7032) Trac plugin creates wrong links
SCM/JIRA link daemon commented on JENKINS-7032 Trac plugin creates wrong links Code changed in jenkins User: Gerd Zanker Path: pom.xml src/main/java/hudson/plugins/trac/TracRepositoryBrowser.java src/test/java/hudson/plugins/trac/TracSvnRepositoryBrowserTest.java src/test/resources/hudson/plugins/trac/changelog-with-deleted-file.xml src/test/resources/hudson/plugins/trac/changelog_unsorted.xml http://jenkins-ci.org/commit/trac-plugin/70dbb9210b77cf46c76dc2330b7d8d6dabd6293e Log: Added test for existing subversion TracRepositoryBrowser class to have a clean, tested base for JENKINS-7032 and JENKINS-13366 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-13366) Prefix or truncate the file path of a change set to build Trac source browser URL
SCM/JIRA link daemon commented on JENKINS-13366 Prefix or truncate the file path of a change set to build Trac source browser URL Code changed in jenkins User: Gerd Zanker Path: pom.xml src/main/java/hudson/plugins/trac/TracRepositoryBrowser.java src/test/java/hudson/plugins/trac/TracSvnRepositoryBrowserTest.java src/test/resources/hudson/plugins/trac/changelog-with-deleted-file.xml src/test/resources/hudson/plugins/trac/changelog_unsorted.xml http://jenkins-ci.org/commit/trac-plugin/70dbb9210b77cf46c76dc2330b7d8d6dabd6293e Log: Added test for existing subversion TracRepositoryBrowser class to have a clean, tested base for JENKINS-7032 and JENKINS-13366 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-16248) URL Trigger plugin doesn't support file:/// URLs
garethbowles created JENKINS-16248 URL Trigger plugin doesnt support file:/// URLs Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: urltrigger Created: 02/Jan/13 9:14 PM Description: I switched to the URL Trigger plugin from the URL Change Trigger since the latter is no longer available in the update center and the former's documentation says that it supports all the latter's functionality. However, when I try polling a file:/// URL (which worked fine with the URL Change Trigger), I get the following error in the polling log: Polling on master. Invoking the url: file:/apps/jenkins/config.xml ERROR - SEVERE - Polling error java.lang.ClassCastException: sun.net.www.protocol.file.FileURLConnection cannot be cast to java.net.HttpURLConnection Full stack trace from Jenkins log: Jan 02, 2013 1:11:24 PM org.jenkinsci.plugins.urltrigger.URLTrigger start SEVERE: Severe error on trigger startup java.lang.ClassCastException: sun.net.www.protocol.file.FileURLConnection cannot be cast to java.net.HttpURLConnection com.sun.jersey.api.client.ClientHandlerException: java.lang.ClassCastException: sun.net.www.protocol.file.FileURLConnection cannot be cast to java.net.HttpURLConnection at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:149) at com.sun.jersey.api.client.Client.handle(Client.java:648) at com.sun.jersey.api.client.WebResource.handle(WebResource.java:670) at com.sun.jersey.api.client.WebResource.get(WebResource.java:191) at org.jenkinsci.plugins.urltrigger.URLTrigger.start(URLTrigger.java:261) at org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:97) at org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:26) at hudson.model.AbstractProject.submit(AbstractProject.java:1868) at hudson.model.Project.submit(Project.java:195) at hudson.model.Job.doConfigSubmit(Job.java:1045) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:722) at sun.reflect.GeneratedMethodAccessor915.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at
[JIRA] (JENKINS-16103) If Anonymous has overall read access, anyone can connect as a slave over JNLP
Jesse Glick commented on JENKINS-16103 If Anonymous has overall read access, anyone can connect as a slave over JNLP Reproducible. core/src/main/resources/hudson/slaves/SlaveComputer/slave-agent.jnlp.jelly has l:isAdminOrTest test="true" which is basically a no-op; it seems to have been this way for years. Should this just be l:hasPermission permission="${Computer.CONNECT}" or similar? 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-13188) Recognize test results from com.github.searls:jasmine-maven-plugin
Alexander Bertram commented on JENKINS-13188 Recognize test results from com.github.searls:jasmine-maven-plugin This is a clever hack, will! But it would still be great to fix so this so that any maven plugin that produces junit-compatible xml will be consumed without having to muck around with plugin order. Is it possible for SurefireArchiver to search for tests after the whole build? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16103) If Anonymous has overall read access, anyone can connect as a slave over JNLP
Jesse Glick closed JENKINS-16103 as Duplicate If Anonymous has overall read access, anyone can connect as a slave over JNLP Refiling. Change By: Jesse Glick (02/Jan/13 10:08 PM) Status: Open Closed Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16110) testng suite support
Chris Cooper commented on JENKINS-16110 testng suite support I'd prefer not to have to attach the whole thing, I think this is a pretty relevant snippet though. ?xml version="1.0" encoding="UTF-8" ? testsuite failures="108" time="2,264.192" errors="0" skipped="6" tests="143" name="TestSuite" I'm pretty sure the problem is because the results file does not start with a testng-results tag. Note in my initial report I posted the file which I'm saving after running my testng suite (I don't get a testng-results.xml file when I run it). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13188) Recognize test results from com.github.searls:jasmine-maven-plugin
Alexander Bertram edited a comment on JENKINS-13188 Recognize test results from com.github.searls:jasmine-maven-plugin This is a clever hack, will! But it would still be great to fix so this so that any maven plugin that produces junit-compatible xml will be consumed without having to muck around with plugin order. Is it possible for SurefireArchiver to search for tests after each module has finished? I am trying to get the renjin-maven-plugin:test goal working on Jenkins, which produces junit xml files from R-language tests, and it would be great to have it work out of the box. 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-11154) Repository_depth_option variable is missing from Source Code Managments
kutzi resolved JENKINS-11154 as Fixed Repository_depth_option variable is missing from Source Code Managments Fixed with JENKINS-777 Change By: kutzi (02/Jan/13 10:30 PM) Status: Open Resolved Assignee: KohsukeKawaguchi kutzi 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-16249) xUnit PHPUNIT group by testsuites
Jonathan Dell created JENKINS-16249 xUnit PHPUNIT group by testsuites Issue Type: Improvement Affects Versions: current Assignee: Gregory Boissinot Components: xunit Created: 02/Jan/13 11:23 PM Description: With multiple testsuites I would like it to group them in the final web report. so it is not just "All Tests" http://i.imgur.com/So3TN.png Project: Jenkins Labels: plugin plugins Priority: Minor Reporter: Jonathan Dell 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-16103) If Anonymous has overall read access, anyone can connect as a slave over JNLP
Kohsuke Kawaguchi deleted JENKINS-16103 If Anonymous has overall read access, anyone can connect as a slave over JNLP 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-15630) Build using Coverity Plugin fails because /tmp/.covlk file exists (Multiple jobs on executor)
SCM/JIRA link daemon commented on JENKINS-15630 Build using Coverity Plugin fails because /tmp/.covlk file exists (Multiple jobs on executor) Code changed in jenkins User: Josh Vinson Path: src/main/java/jenkins/plugins/coverity/CoverityLauncherDecorator.java http://jenkins-ci.org/commit/coverity-plugin/64e49f4c29ac773ef926ee54683d133272805aaf Log: Revert "JENKINS-15630 Build using Coverity Plugin fails because /tmp/.covlk file exists (Multiple jobs on executor)" This reverts commit 93b65fe7f0536abd435af745bafc08ffe5c82464. 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-16239) NPE in getRootDir
Gregory Boissinot commented on JENKINS-16239 NPE in getRootDir Do you have upgraded recently your Jenkins core? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16239) NPE in getRootDir
Gregory Boissinot started work on JENKINS-16239 NPE in getRootDir Change By: Gregory Boissinot (02/Jan/13 11:45 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16248) URL Trigger plugin doesn't support file:/// URLs
Gregory Boissinot commented on JENKINS-16248 URL Trigger plugin doesnt support file:/// URLs You're right. It is not currently supported. Could make a try to the complementary plugin for file: FSTrigger? 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-16248) URL Trigger plugin doesn't support file:/// URLs
Gregory Boissinot started work on JENKINS-16248 URL Trigger plugin doesnt support file:/// URLs Change By: Gregory Boissinot (02/Jan/13 11:45 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16249) xUnit PHPUNIT group by testsuites
Gregory Boissinot started work on JENKINS-16249 xUnit PHPUNIT group by testsuites Change By: Gregory Boissinot (02/Jan/13 11:49 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16249) xUnit PHPUNIT group by testsuites
Gregory Boissinot commented on JENKINS-16249 xUnit PHPUNIT group by testsuites I'll try to look at it. Please upload your test result 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-16248) URL Trigger plugin doesn't support file:/// URLs
garethbowles commented on JENKINS-16248 URL Trigger plugin doesnt support file:/// URLs I didn't know about the FSTrigger plugin. Will try it out and let you know the results. 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-16245) Grails plugin - cannot execute two-word command
Jeff Brown commented on JENKINS-16245 Grails plugin - cannot execute two-word command It sounds like you are not surrounding "tomcat production" with quotes. Is that correct? If you quote them, they should be treated as 1 command with an argument. I hope that makes sense. 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-14538) Separate configure tools page
domi commented on JENKINS-14538 Separate configure tools page sounds good to me, I'll look into it after my vacations - thanks Jesse 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