Seems like root cause of the problem is below:
- Jenkins runs in a local machine on port 8085
- Port forwarding has been setup in gateway
- One can access jenkins using http://gateway:8085 from outside
- Curl http api command succeeds if I use the local IP of the machine
within the network
If I
/JENKINS/Remote+access+API
From: Vinoth raj vinoth@gmail.com
Reply-To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com
Date: Thursday, March 19, 2015 at 10:38 PM
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com
Subject: Unable to get Remote build trigger
On 20.03.2015, at 17:17, Vinoth raj vinoth@gmail.com wrote:
which I think it should not. Not sure what is happening.
The whole point of build trigger tokens is to allow building for users who
usually would not be allowed to.
If you're allowed to trigger builds anyway, you don't need the
@googlegroups.com
Date: Thursday, March 19, 2015 at 10:38 PM
To: jenkinsci-dev@googlegroups.commailto:jenkinsci-dev@googlegroups.com
jenkinsci-dev@googlegroups.commailto:jenkinsci-dev@googlegroups.com
Subject: Unable to get Remote build trigger working
I know this post applies to user group but I haven't have
jenkinsci-dev@googlegroups.com
Date: Thursday, March 19, 2015 at 10:38 PM
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com
Subject: Unable to get Remote build trigger working
I know this post applies to user group but I haven't have found any
response there.
I believe
: Vinoth raj vinoth@gmail.com
Reply-To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com
Date: Thursday, March 19, 2015 at 10:38 PM
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com
Subject: Unable to get Remote build trigger working
I know this post applies
I know this post applies to user group but I haven't have found any
response there.
I believe the developers will be prudent to spot my issue and propose a
solution instantly.
I need to use curl to remotely trigger build for a project.
Jenkins ver. 1.580.3
Following setting is done:
In
