Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-30315

Build Token Root returns 404 error - Possibly Proxy/Auth issue?

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Not A Defect
    • build-token-root-plugin
    • None
    • Ubuntu 14.01
      Jenkins 1.609.2
      Build Root Token Plugin 1.3

    Description

      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}}

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          mcsf M Chon created issue -
          mcsf M Chon made changes -
          Field Original Value New Value
          Description 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           		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}}
          mcsf M Chon made changes -
          Description 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}}           		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}}
          mcsf M Chon made changes -
          Description 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}}           		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}
          mcsf M Chon made changes -
          Description 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}

          		 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}
          mcsf M Chon made changes -
          Description 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}

          		 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}
          mcsf M Chon made changes -
          Description 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}

          		 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}
          mcsf M Chon made changes -
          Description 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}

          		 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}
          mcsf M Chon made changes -
          Description 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}

          		 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}
          mcsf M Chon made changes -
          Description 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}

          		 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}
          mcsf M Chon made changes -
          Description 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}

          		 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}
          mcsf M Chon made changes -
          Description 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}

          		 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}
          mcsf M Chon made changes -
          Description 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}

          		 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}
          jglick Jesse Glick made changes -
          Resolution Not A Defect [ 7 ]
          Status Open [ 1 ] Resolved [ 5 ]
          mcsf M Chon made changes -
          Comment [ Oops!

          OK, I changed my URL but I am still getting a 404:

          $ wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/buildByToken/buildWithParameters?job=mchon_admin&token=SECONDSTREET&FULL_WIPE=false
          [1] 18749
          [2] 18750
          mchon@gollum:~$ --2015-09-08 12:29:26-- https://jenkins.am.sony.com/buildByToken/buildWithParameters?job=mchon_admin
          Resolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.215
          Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.215|:443... connected.
          HTTP request sent, awaiting response... 404 Not Found
          2015-09-08 12:29:26 ERROR 404: Not Found.


          [1]- Exit 8 wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/buildByToken/buildWithParameters?job=mchon_admin
          [2]+ Done token=SECONDSTREET
          ]
          mcsf M Chon made changes -
          Resolution Not A Defect [ 7 ]
          Status Resolved [ 5 ] Reopened [ 4 ]
          jglick Jesse Glick made changes -
          Resolution Not A Defect [ 7 ]
          Status Reopened [ 4 ] Resolved [ 5 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 165410 ] JNJira + In-Review [ 197713 ]

          People

            jglick Jesse Glick
            mcsf M Chon
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: