[JIRA] [p4] (JENKINS-24022) Running 'files' command for multiple hours with a label
Ryan Hummer commented on JENKINS-24022 Running 'files' command for multiple hours with a label Working much better now, thank you! 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] [p4] (JENKINS-24022) Running 'files' command for multiple hours with a label
Paul Allen closed JENKINS-24022 as Fixed Running 'files' command for multiple hours with a label Release 1.0.8 Limit to 50 files and number of reported changes on first build. Change By: Paul Allen (30/Jul/14 4:39 PM) Status: Open Closed 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/d/optout.
[JIRA] [p4] (JENKINS-24022) Running 'files' command for multiple hours with a label
Ryan Hummer created JENKINS-24022 Running 'files' command for multiple hours with a label Issue Type: Bug Affects Versions: current Assignee: Paul Allen Components: p4 Created: 29/Jul/14 9:06 PM Description: I have kicked off a build using the pin job at label functionality, not sure if that is related or not. The job appears to kick off just fine as I see this output: 10:47:59 [EnvInject] - Loading node environment variables. 10:47:59 Building remotely on rsmsnbuild114 in workspace c:\trees 10:48:56 SCM Task: cleanup workspace: RSMSNBUILD114 10:48:57 SCM Task: syncing files at label: my_label 10:48:57 ... sync c:\trees/...@my_label 10:48:57 ... force update false 10:48:57 ... bypass have false It appears the sync works, but I see the machine that runs the Jenkins server under heavy CPU load and the monitor running a 'p4 files'. Is this expected? Project: Jenkins Priority: Major Reporter: Ryan Hummer 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.
