[JIRA] (JENKINS-48551) Cannot select CIFS publish in project configuration
Title: Message Title Corneil du Plessis commented on JENKINS-48551 Re: Cannot select CIFS publish in project configuration I found that when I try to configure the plugin as a Post Step on a build the list of configured shares is blank. However, when I use Post Build Action the plugin does have the list of shares and works as expected. Also when using Configure Jenkins to manage shares there is an "Advanced..." button at the bottom to configure defaults. When selecting Configure defaults also has an empty list of shares. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49023) Cannot upload file using cifs-plugin
Title: Message Title Corneil du Plessis commented on JENKINS-49023 Re: Cannot upload file using cifs-plugin I found that when configuring a Post Build Action the list of shares does display properly. Hopefully, this info may help someone in tracking down the problem. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-utilization] (JENKINS-23132) 4-5min delay at end of job on slave
Corneil du Plessis created JENKINS-23132 4-5min delay at end of job on slave Issue Type: Bug Assignee: Unassigned Components: slave-utilization Created: 21/May/14 3:37 PM Description: We are experiencing a 4-5minute delay on a linux slave at the end of a job. We though it was sending mail but with or without the email step doesn't make a difference. It is not the 'Archiving artifacts' step because it usually takes 15-20s There is not step after the sending mail. The log entries below from different jobs will illustrate. 00:45:20.995 Archiving artifacts 00:45:37.263 Sending e-mails to: xox...@xoxoxoxoxo.xo 00:49:19.280 Finished: SUCCESS 00:18:05.538 Archiving artifacts 00:21:41.815 Finished: SUCCESS 00:44:13.036 Archiving artifacts 00:44:17.691 Checking for post-build 00:44:17.691 Performing post-build step 00:44:17.691 Checking if email needs to be generated 00:44:17.691 Email was triggered for: Success 00:44:17.691 Sending email for trigger: Success 00:44:17.691 Overriding default server settings, creating our own session 00:44:17.700 messageContentType = text/html; charset=UTF-8 00:44:17.702 Adding recipients from recipient list 00:44:17.704 Adding developers 00:44:17.704 Sending to requester 00:44:17.708 Successfully created MimeMessage 00:44:17.708 Sending email to: xox...@xoxoxoxoxo.xo 00:49:18.196 Finished: SUCCESS Environment: Master: Jenkins 1.564, Java 1.6.0_16-b01 os.arch i386 os.name Linux os.version 2.6.32-431.11.2.el6.x86_64 Slave: Project: Jenkins Priority: Major Reporter: Corneil du Plessis 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] [core] (JENKINS-23347) Several minutes delay at end of job
Corneil du Plessis commented on JENKINS-23347 Several minutes delay at end of job Disabling the disk-usage plugin allowed us to get rid of the huge delay at the end of the job. Our workspace has about 80k files. I think the plugin is collecting the info from the slave over the network. Jobs that run on the master or where the workspace has fewer files doesn't suffer the same delay. I don't know enough about the Jenkins Master and Slave interaction to suggest a solution. 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] [safe-restart] (JENKINS-18904) Restarting when builds are running
Corneil du Plessis created JENKINS-18904 Restarting when builds are running Issue Type: Bug Assignee: Unassigned Components: safe-restart Created: 24/Jul/13 10:48 AM Description: I noticed that after we started adding slaves the safe-restart would just restart Jenkins even when builds are still active on master and/or slave Environment: Jenkins 1.520 safe-restart 0.3 Project: Jenkins Priority: Critical Reporter: Corneil du Plessis 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] [cli] (JENKINS-11888) Jenkins CLI does not supports stopping jobs
Corneil du Plessis commented on JENKINS-11888 Jenkins CLI does not supports stopping jobs Calling the command stop-job or cancel-job should make it relatively unambiguous. 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] [skip-certificate-check] (JENKINS-24830) Certificate isn't ignored when using Javamail
Corneil du Plessis created JENKINS-24830 Certificate isn't ignored when using Javamail Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: skip-certificate-check Created: 23/Sep/14 3:42 PM Description: We get the following exception after installing the plugin. javax.mail.MessagingException: Could not connect to SMTP host: mail.tsctech.com, port: 465; nested exception is: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1934) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:638) Is there a way to verify the functioning of the plugin? Project: Jenkins Priority: Critical Reporter: Corneil du Plessis 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] [skip-certificate-check] (JENKINS-24830) Certificate isn't ignored when using Javamail
Corneil du Plessis commented on JENKINS-24830 Certificate isn't ignored when using Javamail Yes, I expected the plugin to ensure that SSL or TLS doesn't checking the certificate since the mail config doesn't provide that option. 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.
