Ticket #1791 (closed defect: fixed)
Opened 2013-04-10T10:01:14-05:00
Last modified 2013-04-10T10:06:35-05:00
Do not use curl inside Jenkins jobs to trigger other Jenkins jobs
| Reported by: | dscho | Owned by: | dscho |
|---|---|---|---|
| Priority: | major | Milestone: |
|
| Component: | Server Admin | Version: | |
| Severity: | serious | Keywords: | |
| Cc: | curtis | Blocked By: | |
| Blocking: | #1608 |
Description
Using curl to trigger Jenkins jobs requires the tokens to be passed as part of the URL. This URL shows up in the publicly visible console log, defeating the purpose of a secret token.
Change History
comment:1 Changed 2013-04-10T10:04:37-05:00 by dscho
comment:2 Changed 2013-04-10T10:06:35-05:00 by dscho
- Status changed from new to closed
- Resolution set to fixed
Inspecting the output of grep -w curl jobs/*/config.xml convinced me that ImageJ triggering ImageJ-launcher was the only problem to be addressed in this issue.
The command-line program jenkins-cli is installed on the Jenkins server. All that was required was to add the public SSH key from ~/.ssh/id_rsa.pub to http://jenkins.imagej.net/user/Jenkins/configure.
Now, the ImageJ job uses jenkins-cli build ImageJ-launcher -p branch=master to trigger building the launcher *iff* the respective sources have changes.