Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Not A Defect
-
None
-
redhat linux 6, running under tomcat
Description
I am new to jenkins and trying to test the "trigger build remotely" feature for some of our jobs. Upon further research I found that I need to use this plugin in order to have "Anonymous" kick off the build.
We are using LDAP authentication via Atlassian crowd for our regular users.
After installing the plugin I created a simple job that only has an "execute shell" build step that has a simple "echo 'test succesful'" inside it.
I use the url https://servername.domainname.com/ops-deploy/buildbyToken/build?jobname=joshtest&token=test
This results in a nullpointer exception. I've verified that the anonymous user has read and build permissions.
I'm trying to access it via the following manner (the --insecure is to ignore the self signed certificate)
curl -i --insecure 'https://servername.domainname.com/ops-deploy/buildByToken/build?jobname=joshtest&token=test'
Attachments
Activity
Josh Love
created issue -
Josh Love
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
I am new to jenkins and trying to test the "trigger build remotely" feature for some of our jobs. Upon further research I found that I need to use this plugin in order to have "Anonymous" kick off the build. We are using LDAP authentication via Atlassian crowd for our regular users. After installing the plugin I created a simple job that only has an "execute shell" build step that has a simple "echo 'test succesful'" inside it. I use the url https://servername.domainname.com/ops-deploy/buildbyToken/build?jobname=joshtest/ This results in a nullpointer exception. I've verified that the anonymous user has read and build (just. I'm trying to access it via the following manner (the --insecure is to ignore the self signed certificate) curl -i --insecure 'https://servername.domainname.com/ops-deploy/buildByToken/build?jobname=joshtest' |
I am new to jenkins and trying to test the "trigger build remotely" feature for some of our jobs. Upon further research I found that I need to use this plugin in order to have "Anonymous" kick off the build. We are using LDAP authentication via Atlassian crowd for our regular users. After installing the plugin I created a simple job that only has an "execute shell" build step that has a simple "echo 'test succesful'" inside it. I use the url https://servername.domainname.com/ops-deploy/buildbyToken/build?jobname=joshtest/ This results in a nullpointer exception. I've verified that the anonymous user has read and build permissions. I'm trying to access it via the following manner (the --insecure is to ignore the self signed certificate) curl -i --insecure 'https://servername.domainname.com/ops-deploy/buildByToken/build?jobname=joshtest' |
Josh Love
made changes -
| Description |
I am new to jenkins and trying to test the "trigger build remotely" feature for some of our jobs. Upon further research I found that I need to use this plugin in order to have "Anonymous" kick off the build. We are using LDAP authentication via Atlassian crowd for our regular users. After installing the plugin I created a simple job that only has an "execute shell" build step that has a simple "echo 'test succesful'" inside it. I use the url https://servername.domainname.com/ops-deploy/buildbyToken/build?jobname=joshtest/ This results in a nullpointer exception. I've verified that the anonymous user has read and build permissions. I'm trying to access it via the following manner (the --insecure is to ignore the self signed certificate) curl -i --insecure 'https://servername.domainname.com/ops-deploy/buildByToken/build?jobname=joshtest' |
I am new to jenkins and trying to test the "trigger build remotely" feature for some of our jobs. Upon further research I found that I need to use this plugin in order to have "Anonymous" kick off the build. We are using LDAP authentication via Atlassian crowd for our regular users. After installing the plugin I created a simple job that only has an "execute shell" build step that has a simple "echo 'test succesful'" inside it. I use the url https://servername.domainname.com/ops-deploy/buildbyToken/build?jobname=joshtest&token=test This results in a nullpointer exception. I've verified that the anonymous user has read and build permissions. I'm trying to access it via the following manner (the --insecure is to ignore the self signed certificate) curl -i --insecure 'https://servername.domainname.com/ops-deploy/buildByToken/build?jobname=joshtest&token=test' |
Josh Love
made changes -
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
| Resolution | Not A Defect [ 7 ] | |
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
| Workflow | JNJira [ 150081 ] | JNJira + In-Review [ 193415 ] |
it's just job - not jobname like I saw on some examples online it seems. Sorry!