[JIRA] (JENKINS-13295) Jenkins hangs for ~1 hour after posting 'Sending Email'
crwong commented on JENKINS-13295 Jenkins hangs for ~1 hour after posting Sending Email We are using the Git plugin v1.1.20, and the ext-email plugin v2.22. It looks like the issue only happens when Jenkins attempts to determine the email address of someone who has checked in code for that build. We use Perforce and Git in our office. The Perforce users are forced to enter valid email addresses when their users are created. However, the Git users are not, and I have only seen this issue with the jobs that use Git. 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-13700) Build hangs during while Sending email
[ https://issues.jenkins-ci.org/browse/JENKINS-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162867#comment-162867 ] crwong commented on JENKINS-13700: -- The other jobs are running perforce. Could have something to do with the email addresses that it is attempting to send to? Not all of the users have email address information enter correctly. Also, I don't see the same errors in my logs as the person who entered bug JENKINS-13102 Build hangs during while Sending email Key: JENKINS-13700 URL: https://issues.jenkins-ci.org/browse/JENKINS-13700 Project: Jenkins Issue Type: Bug Components: core, email-ext Environment: OS: Master: Ubuntu 10.04 Slaves: OSX 1.7.3, Win2K8 Server, Win XP, Win2K3 Server Jenkins: 1.424.1 Plugins: Email-ext plugin: 2.14.1 Configuration Slicing plugin: 1.28.1 Jenkins GIT plugin: 1.1.18 Perforce Plugin: 1.3.9 Reporter: crwong When building on the OSX slave, the build will get to the point where the console says that it is sending email, and it stays there. If you look at the list of executors, the progress bar shows that the build is still on progress. If you look at the job's status page, it looks like the job has completed, and it is no longer running. Clicking on the Stop build button next to the job in the Build Executors Status section, does nothing. The only way to clear the executor is to restart Jenkins. -- 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-13700) Build hangs during while Sending email
[ https://issues.jenkins-ci.org/browse/JENKINS-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162767#comment-162767 ] crwong commented on JENKINS-13700: -- I have a value entered for the Default user e-mail suffix. The only jobs that seem to stall are the jobs using Git. Build hangs during while Sending email Key: JENKINS-13700 URL: https://issues.jenkins-ci.org/browse/JENKINS-13700 Project: Jenkins Issue Type: Bug Components: core, email-ext Environment: OS: Master: Ubuntu 10.04 Slaves: OSX 1.7.3, Win2K8 Server, Win XP, Win2K3 Server Jenkins: 1.424.1 Plugins: Email-ext plugin: 2.14.1 Configuration Slicing plugin: 1.28.1 Jenkins GIT plugin: 1.1.18 Perforce Plugin: 1.3.9 Reporter: crwong When building on the OSX slave, the build will get to the point where the console says that it is sending email, and it stays there. If you look at the list of executors, the progress bar shows that the build is still on progress. If you look at the job's status page, it looks like the job has completed, and it is no longer running. Clicking on the Stop build button next to the job in the Build Executors Status section, does nothing. The only way to clear the executor is to restart Jenkins. -- 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-13700) Build hangs during while Sending email
crwong created JENKINS-13700: Summary: Build hangs during while Sending email Key: JENKINS-13700 URL: https://issues.jenkins-ci.org/browse/JENKINS-13700 Project: Jenkins Issue Type: Bug Components: core, email-ext Environment: OS: Master: Ubuntu 10.04 Slaves: OSX 1.7.3, Win2K8 Server, Win XP, Win2K3 Server Jenkins: 1.424.1 Plugins: Email-ext plugin: 2.14.1 Configuration Slicing plugin: 1.28.1 Jenkins GIT plugin: 1.1.18 Perforce Plugin: 1.3.9 Reporter: crwong When building on the OSX slave, the build will get to the point where the console says that it is sending email, and it stays there. If you look at the list of executors, the progress bar shows that the build is still on progress. If you look at the job's status page, it looks like the job has completed, and it is no longer running. Clicking on the Stop build button next to the job in the Build Executors Status section, does nothing. The only way to clear the executor is to restart Jenkins. -- 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-12313) Duplicate plugin options in project config.
[ https://issues.jenkins-ci.org/browse/JENKINS-12313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162353#comment-162353 ] crwong commented on JENKINS-12313: -- I attempted to resolve the duplicate entry issue by upgrading the deploy plugin, and it only resolved the double entry for the deploy plugin. However, when I upgraded all of the rest of the plugins, my double entry issue went away. Duplicate plugin options in project config. --- Key: JENKINS-12313 URL: https://issues.jenkins-ci.org/browse/JENKINS-12313 Project: Jenkins Issue Type: Bug Components: core, plugin Environment: Jenkins 1.446 RedHat EL 5 x64 Reporter: Rob Petti Priority: Minor Attachments: jenkins-dup-actions.png, jenkins-dup-scm.png After upgrading from 1.362 to 1.446, I'm seeing duplicate options for some plugins in all the job configuration screens. See attached screenshots. Plugins exhibiting this behavior in our environment: VMware Plugin - v0.8 ClearCase Plugin - v0.8.2 Post build task - v1.7 Emotional Hudson Plugin - v1.01 (which I'll probably uninstall entirely) -- 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-12313) Duplicate plugin options in project config.
[ https://issues.jenkins-ci.org/browse/JENKINS-12313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160593#comment-160593 ] crwong commented on JENKINS-12313: -- I am seeing this also, but my list of double entries is much larger. Build-timeout Plugin - v1.4 Hudson Distributed Workspace Clean - v1.0.2 Deploy Plugin - v1.3 Plot - v1.3 Cobertura - v0.8.9 FindBugs - v3.9 PMD - v2.9 Task Scanner - v3.9 Description Setter - v1.4 SCP - v1.5.2 I have another server that is using the same list of plugins, but it does not have the double entries. Is it possible that there is something that got corrupted when I upgraded from version 1.395 to version 1.424.1? Duplicate plugin options in project config. --- Key: JENKINS-12313 URL: https://issues.jenkins-ci.org/browse/JENKINS-12313 Project: Jenkins Issue Type: Bug Components: core, plugin Environment: Jenkins 1.446 RedHat EL 5 x64 Reporter: Rob Petti Priority: Minor Attachments: jenkins-dup-actions.png, jenkins-dup-scm.png After upgrading from 1.362 to 1.446, I'm seeing duplicate options for some plugins in all the job configuration screens. See attached screenshots. Plugins exhibiting this behavior in our environment: VMware Plugin - v0.8 ClearCase Plugin - v0.8.2 Post build task - v1.7 Emotional Hudson Plugin - v1.01 (which I'll probably uninstall entirely) -- 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-8082) git plugin multi-repo can't work
[ https://issues.jenkins-ci.org/browse/JENKINS-8082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159724#comment-159724 ] crwong commented on JENKINS-8082: - I am not sure I understand why this is marked as Won't Fix. The Hudson version of the git plugin is marked as Fixed. I have one project that has its source in one repo and the framework that it uses in another repo, and I would like to be able to use the plugin to pull both the source for the project and the source for the framework. git plugin multi-repo can't work Key: JENKINS-8082 URL: https://issues.jenkins-ci.org/browse/JENKINS-8082 Project: Jenkins Issue Type: Bug Components: git Affects Versions: current Environment: git plugin 1.1 Reporter: bwilliams Assignee: abayer In the git plugin, you have the ability to watch multiple repos, but then you clone them into the same dir, so the git checkouts show you all of one repo, but not the others. The local subdirectory for repo and probably branches to build need to be per repository, not for all. -- 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
