Hi All, I would like to ask how the "Changes" information are pulled from source control location.
Here is my setup. I am using Team Foundation Server plugin and use poll for change every hour. There is a Gated Build Definition configured in our TFS Server that builds the project before any developer can check-in their code to TFS. So our process is to make sure there will no compilation errors before a developer checks in a code. Every hour if there is a change we run a CI process using Jenkins to run more tests. I found that the "changes' information like who checked-in the latest code was using a build account name, not the actual developer who checked-in the code. Here is an example: Summary 1. Testing CI tests run * Version 123456 by builder_account: * Testing CI tests run [image: The file was modified]$/TeamProject/ProjectA/login.js I check the changeset details via VS IDE and the change 123456 was checked-in by developerA. How come in the "changes" it listed the builder_account which is our tfs build user account? I also did a quick "tf history" command and it listed that developerA checked in that latest changeset 123456. This behavior only shows if I have a "Gated" build setup in the TFS Server side. If I don't have a gated build definition setup, it shows the correct information in the "Changes" details. Summary 1. Testing CI tests run * Version 123456 by developerA: * Testing CI tests run [image: The file was modified]$/TeamProject/ProjectA/login.js Is there a way that I can retrieve the correct user if I use a Gated Build Definition? Do I need to reconfigure something in my setup? Would appreciate for any inputs. Neil -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3f988153-89f0-4d3c-8397-8b445550401d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
