It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,884
×10,917

question asked: Feb 20 '17, 8:56 p.m.
question was seen: 1,121 times
last updated: Feb 20 '17, 9:05 p.m.

Related questions

Automated build requests with custom buildRequesterUserId property get started with an admin ID

0
kanjbala jawahar (60●1●8●16) | asked Feb 20 '17, 8:56 p.m.
edited Feb 20 '17, 9:03 p.m.
The automated build requests are not using buildRequesterUserId for "requestor." Rather they are using the admin ID.
The automation sets the buildRequesterUserId using the code:

propFromGUI = !(value.isEmpty()) ? BuildItemFactory.createBuildProperty("buildRequesterUserId", value) : 
                            BuildItemFactory.createBuildProperty("buildRequesterUserId", adminEmail); 

I can see from the logs and the build requests that are kicked off that buildRequesterUserId is set to the non-admin email (the email of the user requesting the build via rest service). But the builds are still being kicked of by admin ID! 

Is there something that can be done to fix this or this is how it will be when the logged in user (admin) is not the same as the user in the buildRequesterUserId?

 This question is similar to another I saw here:


Comments
kanjbala jawahar commented Feb 20 '17, 9:04 p.m. | edited Feb 20 '17, 9:05 p.m.

 Build is requested using the code:


buildRequest = buildReqClient.requestBuild(buildDef, modifiedProps, null, true, false, monitor);

where modifiedProps contains the custom properties.

Be the first one to answer this question!

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.