User not passing to job history if submitted by URL?

[Don Alcombright]

We have an internal build page setup that passes builds off via URL. This method works fine but for some reason, although the job passes fine with

http://username:apitoken@jenkins-server....

the build history doesn't show the user that kicked it off. If i submit via the UI of Jenkins it does. Any thoughts on what I am doing wrong?

[Daniel Beck]

> On 02.02.2017, at 20:26, Don Alcombright <don.alc...@gmail.com> wrote:
>
> Any thoughts on what I am doing wrong?

You forgot to include the interesting parts of the URL you're using. Strip out job names or whatever, but leave the rest intact.

Also, what does Jenkins tell you is the cause for the build, if not the user triggering it?

[Don Alcombright]

http://username:TOKEN@MACHINENAME:8080/job/CATRADER%20Suite%20Builder/buildWithParameters?token=ctbuild&BuildDatabases=False&BuildWorkstation=True&BuildReports=False&BuildLossfiles=False&ctreltype=Nightly&ctrelver=Automation&ctrelname=Nightly&builddestination=\\PATHTOFOLDER&isversion=2015&Email_Recipients=bl...@blah.com

All it says next to the user is N/A, if I login to jenkins and kick it off it gets my AD user like it should.

[Daniel Beck]

Could be related to use of the build token. Try without, and make sure your user has Build permission.

[Don Alcombright]

how do I tell it what do build without the build token? I thought that was required for remote building?

[Don Alcombright]

So its improving sort of haha. Now instead of "N/A" it posts "anonymous" any thoughts on that?

On Friday, February 3, 2017 at 10:21:43 AM UTC-5, Daniel Beck wrote:

[Daniel Beck]

> On 06.02.2017, at 14:41, Don Alcombright <don.alc...@gmail.com> wrote:
>
> any thoughts on that?

Build token is needed if and only if whoever you authenticate as has permission to view, but not build, the job.

Clearly, no authentication happens here, probably because Jenkins doesn't ask for it. Read https://wiki.jenkins-ci.org/display/JENKINS/Authenticating+scripted+clients