[JENKINS-30315] Build Token Root returns 404 error - Possibly Proxy/Auth issue? - Jenkins Jira

Type: Bug
Resolution: Not A Defect
Priority: Minor
Component/s: build-token-root-plugin
Labels:
None
Environment:
Ubuntu 14.01
Jenkins 1.609.2
Build Root Token Plugin 1.3

Similar Issues:
Powered by SuggestiMate

Show

Our Jenkins servers require "auth-no-challenge" and "no-proxy" flags to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================

$ wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@gollum:~/cid-dev/Cid$ 2015-09-04 15:02:30 https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET

===============================
buildByToken URI, fails:
===============================

{{$ wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@gollum:~/cid-dev/Cid$ 2015-09-04 15:03:33 https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}

M Chon created issue - 2015-09-04 22:10

M Chon made changes - 2015-09-04 22:11

Description

Original: Our Jenkins servers require --auth-no-challenge and --no-proxy flags to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
$ wget -v --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)... 43.148.4.200
Connecting to ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET

===============================
buildByToken URI, fails:
===============================
$ wget --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)... 43.148.4.200
Connecting to ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET

New: Our Jenkins servers require {{--auth-no-challenge}} and{{ --no-proxy flags}} to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{{$ wget -v --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)... 43.148.4.200
Connecting to ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET}}

===============================
buildByToken URI, fails:
===============================
{{$ wget --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)... 43.148.4.200
Connecting to ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}

M Chon made changes - 2015-09-04 22:12

Description

Original: Our Jenkins servers require {{--auth-no-challenge}} and{{ --no-proxy flags}} to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{{$ wget -v --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)... 43.148.4.200
Connecting to ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET}}

===============================
buildByToken URI, fails:
===============================
{{$ wget --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)... 43.148.4.200
Connecting to ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}

New: Our Jenkins servers require {{--auth-no-challenge}} and {{--no-proxy flags}} to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{quote}$ wget -v --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)... 43.148.4.200
Connecting to ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}

===============================
buildByToken URI, fails:
===============================
{{$ wget --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)... 43.148.4.200
Connecting to ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}

M Chon made changes - 2015-09-04 22:13

Description

Original: Our Jenkins servers require {{--auth-no-challenge}} and {{--no-proxy flags}} to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{quote}$ wget -v --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)... 43.148.4.200
Connecting to ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}

===============================
buildByToken URI, fails:
===============================
{{$ wget --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)... 43.148.4.200
Connecting to ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}

New: Our Jenkins servers require --auth-no-challenge and {{--no-proxy flags}} to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{quote}$ wget -v --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)... 43.148.4.200
Connecting to ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}

===============================
buildByToken URI, fails:
===============================
{quote}{{$ wget --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)... 43.148.4.200
Connecting to ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}{quote}

M Chon made changes - 2015-09-04 22:15

Description

Original: Our Jenkins servers require --auth-no-challenge and {{--no-proxy flags}} to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{quote}$ wget -v --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)... 43.148.4.200
Connecting to ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}

===============================
buildByToken URI, fails:
===============================
{quote}{{$ wget --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)... 43.148.4.200
Connecting to ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}{quote}

New: Our Jenkins servers require --auth-no-challenge and {{--no-proxy flags}} to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{quote}$ wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}

===============================
buildByToken URI, fails:
===============================
{quote}{{$ wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}{quote}

M Chon made changes - 2015-09-04 22:15

Description

Original: Our Jenkins servers require --auth-no-challenge and {{--no-proxy flags}} to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{quote}$ wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}

===============================
buildByToken URI, fails:
===============================
{quote}{{$ wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}{quote}

New: Our Jenkins servers require {{--auth-no-challenge}} and {{--no-proxy flags}} to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{quote}$ wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}

===============================
buildByToken URI, fails:
===============================
{quote}{{$ wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}{quote}

M Chon made changes - 2015-09-04 22:16

Description

Original: Our Jenkins servers require {{--auth-no-challenge}} and {{--no-proxy flags}} to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{quote}$ wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}

===============================
buildByToken URI, fails:
===============================
{quote}{{$ wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}{quote}

New: Our Jenkins servers require --auth-no-challenge and --no-proxy flags to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{quote}$ wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}

===============================
buildByToken URI, fails:
===============================
{quote}{{$ wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}{quote}

M Chon made changes - 2015-09-04 22:16

Description

Original: Our Jenkins servers require --auth-no-challenge and --no-proxy flags to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{quote}$ wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}

===============================
buildByToken URI, fails:
===============================
{quote}{{$ wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}{quote}

New: Our Jenkins servers require *{{--auth-no-challenge}}* and *{{--no-proxy}}* flags to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{quote}$ wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}

===============================
buildByToken URI, fails:
===============================
{quote}{{$ wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}{quote}

M Chon made changes - 2015-09-04 22:17

Description

Original: Our Jenkins servers require *{{--auth-no-challenge}}* and *{{--no-proxy}}* flags to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{quote}$ wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}

===============================
buildByToken URI, fails:
===============================
{quote}{{$ wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}{quote}

New: Our Jenkins servers require *--auth-no-challenge* and *--no-proxy* flags to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{quote}$ wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}

===============================
buildByToken URI, fails:
===============================
{quote}{{$ wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}{quote}

M Chon made changes - 2015-09-04 22:18

Description

Original: Our Jenkins servers require *--auth-no-challenge* and *--no-proxy* flags to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{quote}$ wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}

===============================
buildByToken URI, fails:
===============================
{quote}{{$ wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}{quote}

New: Our Jenkins servers require *--auth-no-challenge* and *--no-proxy* flags to be passed to wget when triggering builds.
I installed the Build Root Token Plugin today and attempted to use the buildByToken URI.
It failed. It is not clear why.
The documentation indicates it should "just work".
The only thing different about my environment are the flags which need to be passed to wget.

===============================
Regular URI, is successful:
===============================
{quote}$ wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22861
mchon@gollum:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 201 Created
Length: 0
Saving to: ‘buildWithParameters?token=SECONDSTREET.3’

[ <=> ] 0 --.-K/s in 0s

2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0]

[1]+ Done wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}

===============================
buildByToken URI, fails:
===============================
{quote}{{$ wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET&FULL_WIPE=false
[1] 22948
mchon@gollum:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET
Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200
Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-09-04 15:03:34 ERROR 404: Not Found.

[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}{quote}

Assignee:: Jesse Glick

Reporter:: M Chon

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2015-09-04 22:10

Updated:: 2015-09-08 20:10

Resolved:: 2015-09-08 19:56

Jenkins

Details

Description

Attachments

Activity

[JENKINS-30315] Build Token Root returns 404 error - Possibly Proxy/Auth issue?

People

Dates