-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
Platform: All, OS: All
-
Powered by SuggestiMate
We used to have users' email addresses looked up in Perforce, but it has stopped
working. I think this happened in the 1.0.15 release of the plugin.
I found issue 1374 which was a request to implement this lookup in the first
place, and stumbled upon issue 1022 where the submitter mentions a change to
PerforceMailResolver in October (fits with 1.0.15).
Symptom: Mail is sent to "username" instead of "email address" (for users not
already registered in Hudson's list of people).
[JENKINS-4933] User email address lookup in Perforce stopped working
No, not using Matrix builds (yet - am considering it, but hesitant).
Yes, have some slaves. I haven't verified whether email lookup only fails on
slaves or also on Master.
As far as I recall, the email lookup used to take place at the end of the build,
when/if it was necessary in order to blame someone. But I could be wrong.
Yes, I can (and have) edit the users when this happens, which it fortunately
rarely does these days, but a fix would definitely be nice. I agree that matrix
builds are more important, though
The work-around of adding users' emails manually doesn't really work for installations with 270+ users, unfortunately.
As near as I can tell, the mail resolver was working fine before this change, though you are completely right in fixing the instance variable at the expense of this functionality.
I'll take a look at it to see if I can't get it working again, but it looks like it will be pretty complicated.
If performing a (simple) user lookup is so difficult to add in the code, then I'd be afraid to even look at it
On a serious note, there's no requirement that the user lookup is the last thing to be done, so if it's possible to perform it during checkout/polling/whenever, before any distribution takes place, then perhaps that's a working solution? The user(s) in question obviously have touched the code, so their email addresses are interesting - we might not need it on /this/ build, but we're almost certain to need it /sometime/.
Code changed in hudson
User: : rpetti
Path:
trunk/hudson/plugins/perforce/src/main/java/hudson/plugins/perforce/PerforceMailResolver.java
http://fisheye4.cenqua.com/changelog/hudson/?cs=24485
Log:
[FIXED JENKINS-4933] fixed perforce email resolution. It should now work normally again.
I've submitted a fix to the trunk. It appears to work fine in my tests using both a master build and a slave build, but more testing is certainly welcome.
I am seeing the same issue with the my test Hudson server.
OS: Win2K3 Server
Hudson: 1.343
Perforce Plugin: 1.0.18
I submit a change to perforce with user "cwong", and I waited for a build to be triggered. At the end of the build, Hudson attempts to send email. Rather than the plugin determining my email address, I got the following message:
"Failed to send e-mail to cwong because no e-mail address is known, and no default e-mail domain is configured"
I found some more information in the Hudson log. It looks like it is having trouble running "p4 user -o USER"
INFO | jvm 1 | 2010/02/06 00:14:05 | [test2] $ c:\Perforce\p4.exe user -o cwong
INFO | jvm 1 | 2010/02/06 00:21:27 | 12057594 Handling GET /scm/PerforceSCM/validatePerforceLogin : RequestHandlerThread[#6] INFO perforce - Executing: c:\Perforce\p4.exe counter change
INFO | jvm 1 | 2010/02/06 00:21:28 | 12057937 Handling GET /scm/PerforceSCM/validatePerforceLogin : RequestHandlerThread[#6] INFO perforce - Executing: c:\Perforce\p4.exe user -o
INFO | jvm 1 | 2010/02/06 00:21:28 | 12058328 Handling GET /scm/PerforceSCM/validateP4Client : RequestHandlerThread[#6] INFO perforce - Executing: c:\Perforce\p4.exe counter change
INFO | jvm 1 | 2010/02/06 00:21:28 | 12058672 Handling GET /scm/PerforceSCM/validateP4Client : RequestHandlerThread[#6] INFO perforce - Executing: c:\Perforce\p4.exe workspace -o cwong_test2_ups
INFO | jvm 1 | 2010/02/06 00:21:29 | 12059062 Handling GET /scm/PerforceSCM/checkChangeList : RequestHandlerThread[#6] INFO perforce - Executing: c:\Perforce\p4.exe counter change
INFO | jvm 1 | 2010/02/06 00:38:07 | 13057437 Executor #0 for sbconnectbld01 : executing test2 #57 WARN perforce - Perforce process terminated suddenly
INFO | jvm 1 | 2010/02/06 00:38:07 | 13057437 Executor #0 for sbconnectbld01 : executing test2 #57 WARN perforce - java.io.InterruptedIOException
INFO | jvm 1 | 2010/02/06 00:38:07 | at java.io.PipedInputStream.read(PipedInputStream.java:312)
INFO | jvm 1 | 2010/02/06 00:38:07 | at java.io.PipedInputStream.read(PipedInputStream.java:361)
INFO | jvm 1 | 2010/02/06 00:38:07 | at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
INFO | jvm 1 | 2010/02/06 00:38:07 | at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
INFO | jvm 1 | 2010/02/06 00:38:07 | at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
INFO | jvm 1 | 2010/02/06 00:38:07 | at java.io.InputStreamReader.read(InputStreamReader.java:167)
INFO | jvm 1 | 2010/02/06 00:38:07 | at java.io.BufferedReader.fill(BufferedReader.java:136)
INFO | jvm 1 | 2010/02/06 00:38:07 | at java.io.BufferedReader.readLine(BufferedReader.java:299)
INFO | jvm 1 | 2010/02/06 00:38:07 | at java.io.BufferedReader.readLine(BufferedReader.java:362)
INFO | jvm 1 | 2010/02/06 00:38:07 | at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292)
INFO | jvm 1 | 2010/02/06 00:38:07 | at com.tek42.perforce.parse.Users.getUser(Users.java:52)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.plugins.perforce.PerforceMailResolver.findMailAddressFor(PerforceMailResolver.java:32)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:81)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:476)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.tasks.MailSender.buildCulpritList(MailSender.java:357)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.tasks.MailSender.createEmptyMail(MailSender.java:338)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.tasks.MailSender.createBackToNormalMail(MailSender.java:156)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.tasks.MailSender.getMail(MailSender.java:147)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.tasks.MailSender.execute(MailSender.java:81)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.tasks.Mailer.perform(Mailer.java:99)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:582)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.model.AbstractBuild$AbstractRunner.performAllBuildStep(AbstractBuild.java:563)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.model.AbstractBuild$AbstractRunner.performAllBuildStep(AbstractBuild.java:550)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.model.Build$RunnerImpl.post2(Build.java:152)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.model.Run.run(Run.java:1221)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.model.ResourceController.execute(ResourceController.java:88)
INFO | jvm 1 | 2010/02/06 00:38:07 | at hudson.model.Executor.run(Executor.java:122)
INFO | jvm 1 | 2010/02/06 00:38:07 |
INFO | jvm 1 | 2010/02/06 00:38:07 | Could not get email address from Perforce: No output for: c:\Perforce\p4.exe user -o cwong
Thanks crwong. More information about your master/slave setup would be appreciated.
My test setup is composed of the master and one slave.
OS for Master and Slave: Win2K3
Slave launched using JNPL
Java on Master and Slave: jdk1.6.0_06
Are your jobs able to run on both the master and the slave? Mail resolution always takes place on the master, so if for some reason the perforce configuration doesn't work on it, then emails will not be resolved.
The build was tied to the slave, but I have changed it so that it can build on either the master or the slave. The results for the builds on the master is the same as when the build is run on the slave.
So you are saying that email resolution still doesn't work? Is the stack trace identical to the one you posted above?
There has been some interesting behavior since my last posting. There were a total of 5 builds yesterday on the master. The first three builds were unable to determine my email address. For some reason, the fourth build (#71) determined my email address, and I received email for the build. I looked at the user information for Hudson, and there is a user that has my perforce user name and now it has my email address associated with it. I am going to attach the log that covers what was going on on that server for that time span.
To give you a better idea of what was happening, I am listing the build numbers, and what triggered the builds.
#68 - I triggered the build with user cwong1
#69 - I triggered the build with user cwong1
#70 - Build was triggered by a change I made in perforce with user cwong
#71 - Build was triggered by a change another user made in perforce
#72 - Build was triggered by a change another user made in perforce
So, the answers to your question about the email working is that it did not at first, and then it started working. The stack trace looked the same for the first build on the master, but after that, it looks like it stopped performing the "GET".
This file contains the log output that Hudson generated when I had the builds running on the master. The strange thing that happened on Hudson was that the perforce plugin could not determine my email information for the first three of the five builds.
Another interesting bit of information is that the console output still says that it can not determine my email address. I pasted that portion of the console output below.
"Failed to send e-mail to cwong because no e-mail address is known, and no default e-mail domain is configured
Sending e-mails to: clint_wong@intuit.com"
It either successfully determined the email address at one point, or someone entered the username and email manually into hudson. In the event that it can't determine the email from the SCM plugin, hudson falls back to what is saved under the user name.
Also the "GET" that you are seeing in the logs is for input field validation on the configuration page. It actually has nothing to do with email resolution.
I'm going to see if I can add some additional logging to the next release so we can see what's going on here.
I installed v1.0.20, and it appear to have less output than before. I placed a copy of the log below.
INFO | jvm 1 | 2010/02/16 13:07:58 | INFO: Completed initialization
INFO | jvm 1 | 2010/02/16 13:08:01 | Feb 16, 2010 1:08:01 PM org.springframework.context.support.AbstractApplicationContext prepareRefresh
INFO | jvm 1 | 2010/02/16 13:08:01 | INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@d006a7: display name [Root WebApplicationContext]; startup date [Tue Feb 16 13:08:01 PST 2010]; root of context hierarchy
INFO | jvm 1 | 2010/02/16 13:08:01 | Feb 16, 2010 1:08:01 PM org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactory
INFO | jvm 1 | 2010/02/16 13:08:01 | INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@d006a7]: org.springframework.beans.factory.support.DefaultListableBeanFactory@9aa764
INFO | jvm 1 | 2010/02/16 13:08:01 | Feb 16, 2010 1:08:01 PM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO | jvm 1 | 2010/02/16 13:08:01 | INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@9aa764: defining beans [activeDirectory,authenticationManager]; root of factory hierarchy
INFO | jvm 1 | 2010/02/16 13:08:01 | Feb 16, 2010 1:08:01 PM org.springframework.context.support.AbstractApplicationContext prepareRefresh
INFO | jvm 1 | 2010/02/16 13:08:01 | INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@13e4653: display name [Root WebApplicationContext]; startup date [Tue Feb 16 13:08:01 PST 2010]; root of context hierarchy
INFO | jvm 1 | 2010/02/16 13:08:01 | Feb 16, 2010 1:08:01 PM org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactory
INFO | jvm 1 | 2010/02/16 13:08:01 | INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@13e4653]: org.springframework.beans.factory.support.DefaultListableBeanFactory@1d4ab05
INFO | jvm 1 | 2010/02/16 13:08:01 | Feb 16, 2010 1:08:01 PM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO | jvm 1 | 2010/02/16 13:08:01 | INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@1d4ab05: defining beans [filter,legacy]; root of factory hierarchy
INFO | jvm 1 | 2010/02/16 13:08:01 | Feb 16, 2010 1:08:01 PM hudson.TcpSlaveAgentListener <init>
INFO | jvm 1 | 2010/02/16 13:08:01 | INFO: JNLP slave agent listener started on TCP port 1651
INFO | jvm 1 | 2010/02/16 13:08:11 | Feb 16, 2010 1:08:11 PM hudson.TcpSlaveAgentListener$ConnectionHandler run
INFO | jvm 1 | 2010/02/16 13:08:11 | INFO: Accepted connection #1 from /172.17.83.47:3913
INFO | jvm 1 | 2010/02/16 13:11:40 | Feb 16, 2010 1:11:40 PM hudson.triggers.SCMTrigger$Runner run
INFO | jvm 1 | 2010/02/16 13:11:40 | INFO: SCM changes detected in test2. Triggering #97
INFO | jvm 1 | 2010/02/16 13:14:49 | Feb 16, 2010 1:14:49 PM hudson.model.Run run
INFO | jvm 1 | 2010/02/16 13:14:49 | INFO: test2 #97 main build action completed: FAILURE
It looks to me like everything worked... that's why there's no log output.
What does the console log say?
The console output has not changed. I have been using two different users for making perforce submissions, and the plugin is not able to determine the email address.
Failed to send e-mail to cwong because no e-mail address is known, and no default e-mail domain is configured
Failed to send e-mail to scm because no e-mail address is known, and no default e-mail domain is configured
Something else is going on, because it's not even trying to resolve the email address. Does your slave stay up after it's done building? Can you delete all previous builds, restart the server and try again? Also, make sure that there are no entries for these users saved in hudson. That error is consistent with a saved user that has their email field set to nothing.
I deleted all of the old builds and the hudson user with the exception of the cwong1 user. The build failed with the console output
Failed to send e-mail to scm because no e-mail address is known, and no default e-mail domain is configured
Failed to send e-mail to cwong because no e-mail address is known, and no default e-mail domain is configured
The hudson log output states that it can not run the perforce command (see below).
INFO | jvm 1 | 2010/02/17 12:24:08 | 7373891 Handling GET /scm/PerforceSCM/validatePerforceLogin : RequestHandlerThread[#0] INFO perforce - Executing: c:\Perforce\p4.exe counter change
INFO | jvm 1 | 2010/02/17 12:24:08 | 7374266 Handling GET /scm/PerforceSCM/validatePerforceLogin : RequestHandlerThread[#0] INFO perforce - Executing: c:\Perforce\p4.exe user -o
INFO | jvm 1 | 2010/02/17 12:24:11 | 7376906 Handling GET /scm/PerforceSCM/validateP4Client : RequestHandlerThread[#0] INFO perforce - Executing: c:\Perforce\p4.exe counter change
INFO | jvm 1 | 2010/02/17 12:24:11 | 7377234 Handling GET /scm/PerforceSCM/validateP4Client : RequestHandlerThread[#0] INFO perforce - Executing: c:\Perforce\p4.exe workspace -o cwong_test2_ups
INFO | jvm 1 | 2010/02/17 12:24:11 | 7377594 Handling GET /scm/PerforceSCM/checkChangeList : RequestHandlerThread[#0] INFO perforce - Executing: c:\Perforce\p4.exe counter change
INFO | jvm 1 | 2010/02/17 12:24:28 | 7394609 Handling GET /scm/PerforceSCM/validatePerforceLogin : RequestHandlerThread[#3] INFO perforce - Executing: c:\Perforce\p4.exe counter change
INFO | jvm 1 | 2010/02/17 12:24:29 | 7394953 Handling GET /scm/PerforceSCM/validatePerforceLogin : RequestHandlerThread[#3] INFO perforce - Executing: c:\Perforce\p4.exe user -o
INFO | jvm 1 | 2010/02/17 12:24:29 | 7395328 Handling GET /scm/PerforceSCM/validateP4Client : RequestHandlerThread[#3] INFO perforce - Executing: c:\Perforce\p4.exe counter change
INFO | jvm 1 | 2010/02/17 12:24:29 | 7395656 Handling GET /scm/PerforceSCM/validateP4Client : RequestHandlerThread[#3] INFO perforce - Executing: c:\Perforce\p4.exe workspace -o cwong_test2_ups
INFO | jvm 1 | 2010/02/17 12:24:30 | 7396016 Handling GET /scm/PerforceSCM/checkChangeList : RequestHandlerThread[#3] INFO perforce - Executing: c:\Perforce\p4.exe counter change
INFO | jvm 1 | 2010/02/17 12:31:54 | Feb 17, 2010 12:31:54 PM hudson.model.Run run
INFO | jvm 1 | 2010/02/17 12:31:54 | INFO: test2 #100 main build action completed: FAILURE
INFO | jvm 1 | 2010/02/17 12:31:54 | [vault] $ c:\Perforce\p4.exe user -o scm
INFO | jvm 1 | 2010/02/17 12:31:54 | Could not get email address from Perforce: Could not run perforce command.
INFO | jvm 1 | 2010/02/17 12:31:54 | [vault] $ c:\Perforce\p4.exe user -o cwong
INFO | jvm 1 | 2010/02/17 12:31:54 | Could not get email address from Perforce: Could not run perforce command.
The error message suggests that c:\perforce\p4.exe either doesn't exist, or doesn't run for some reason. I'm not sure why, but you don't seem to be getting a full stack trace for some reason, and without that I can't really help you any further.
I switch the build to stop building on the slave and made it build on the master. The results of this change caused the email to work for all but one user.
INFO | jvm 1 | 2010/02/17 14:21:25 | Feb 17, 2010 2:21:25 PM hudson.triggers.SCMTrigger$Runner run
INFO | jvm 1 | 2010/02/17 14:21:25 | INFO: SCM changes detected in test2. Triggering #106
INFO | jvm 1 | 2010/02/17 14:24:33 | Feb 17, 2010 2:24:33 PM hudson.model.Run run
INFO | jvm 1 | 2010/02/17 14:24:33 | INFO: test2 #106 main build action completed: FAILURE
INFO | jvm 1 | 2010/02/17 14:24:33 | [data] $ c:\\Perforce
p4.exe user -o pt
INFO | jvm 1 | 2010/02/17 14:24:33 | 989172 Executor #0 for master : executing test2 #106 WARN perforce - Perforce process terminated suddenly
INFO | jvm 1 | 2010/02/17 14:24:33 | 989172 Executor #0 for master : executing test2 #106 WARN perforce - java.io.InterruptedIOException
INFO | jvm 1 | 2010/02/17 14:24:33 | at java.io.PipedInputStream.read(PipedInputStream.java:312)
INFO | jvm 1 | 2010/02/17 14:24:33 | at java.io.PipedInputStream.read(PipedInputStream.java:361)
INFO | jvm 1 | 2010/02/17 14:24:33 | at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
INFO | jvm 1 | 2010/02/17 14:24:33 | at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
INFO | jvm 1 | 2010/02/17 14:24:33 | at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
INFO | jvm 1 | 2010/02/17 14:24:33 | at java.io.InputStreamReader.read(InputStreamReader.java:167)
INFO | jvm 1 | 2010/02/17 14:24:33 | at java.io.BufferedReader.fill(BufferedReader.java:136)
INFO | jvm 1 | 2010/02/17 14:24:33 | at java.io.BufferedReader.readLine(BufferedReader.java:299)
INFO | jvm 1 | 2010/02/17 14:24:33 | at java.io.BufferedReader.readLine(BufferedReader.java:362)
INFO | jvm 1 | 2010/02/17 14:24:33 | at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292)
INFO | jvm 1 | 2010/02/17 14:24:33 | at com.tek42.perforce.parse.Users.getUser(Users.java:52)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.plugins.perforce.PerforceMailResolver.findMailAddressFor(PerforceMailResolver.java:45)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:81)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:476)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.tasks.MailSender.buildCulpritList(MailSender.java:357)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.tasks.MailSender.createEmptyMail(MailSender.java:338)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.tasks.MailSender.createFailureMail(MailSender.java:206)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.tasks.MailSender.getMail(MailSender.java:133)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.tasks.MailSender.execute(MailSender.java:81)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.tasks.Mailer.perform(Mailer.java:99)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:582)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.model.AbstractBuild$AbstractRunner.performAllBuildStep(AbstractBuild.java:563)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.model.AbstractBuild$AbstractRunner.performAllBuildStep(AbstractBuild.java:550)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.model.Build$RunnerImpl.post2(Build.java:152)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.model.Run.run(Run.java:1221)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.model.ResourceController.execute(ResourceController.java:88)
INFO | jvm 1 | 2010/02/17 14:24:33 | at hudson.model.Executor.run(Executor.java:122)
INFO | jvm 1 | 2010/02/17 14:24:33 |
INFO | jvm 1 | 2010/02/17 14:24:33 | Could not get email address from Perforce: No output for: c:\\Perforce
p4.exe user -o pt
INFO | jvm 1 | 2010/02/17 14:24:33 | [data] $ c:\\Perforce
p4.exe user -o cwong
DEBUG | wrapperp | 2010/02/17 14:24:33 | send a packet PING : ping
INFO | jvm 1 | 2010/02/17 14:24:33 | WrapperManager Debug: Received a packet PING : ping
INFO | jvm 1 | 2010/02/17 14:24:33 | WrapperManager Debug: Send a packet PING : ping
DEBUG | wrapperp | 2010/02/17 14:24:33 | read a packet PING : ping
INFO | jvm 1 | 2010/02/17 14:24:34 | [data] $ c:\\Perforce
p4.exe user -o scm
INFO | jvm 1 | 2010/02/17 14:24:34 | [data] $ c:\\Perforce
p4.exe user -o ajerjiss
INFO | jvm 1 | 2010/02/17 14:24:34 | [data] $ c:\\Perforce
p4.exe user -o cblankenship
INFO | jvm 1 | 2010/02/17 14:24:35 | [data] $ c:\\Perforce
p4.exe user -o rramanat
INFO | jvm 1 | 2010/02/17 14:24:35 | [data] $ c:\\Perforce
p4.exe user -o johara
Were you using Matrix builds, or did you have any slave nodes? I'm the one who
made the change to the PerforceMailResolver. It was relying on an instance
variable that was volitile in a distributed build environment. I suspect that
it only worked when there was only one node, or perhaps it worked so long as it
was called before any distributed builds had run. I didn't see any way to fix
it while also supporting distributed matrix builds.
Isn't there a simple workaround in that you can just edit the user's information
to set the email address manually? I realize that's not ideal, but there's no
equivalent workaround for broken distributed builds, so unless someone can
figure out how to support both, I think the distributed builds are more
important than getting email addresses from perforce. I'm sure it is possible
to do both, I just didn't see how when I looked at it.