Use variables in command line options for Job references
Reported by Matt | September 5th, 2011 @ 03:15 AM | in Rundeck 1.4 (closed)
I think i've raised similar before, but not quite this use case.
Running a job in Dispatch to Nodes:
step 1. echo "${node.privateDnsName}" - this works and outputs
the node the step is running on
step 2. run another job and supply '-node ${node.privateDnsName}'
as a commandline option. - this fails and actually passes the text
rather than the value of node.privateDnsName.
Comments and changes to this ticket
-
Greg Schueler October 19th, 2011 @ 02:55 PM
- Tag set to “job reference, bug”
- Milestone set to “Rundeck 1.4”
- Milestone order changed from “95” to “0”
-
Greg Schueler October 19th, 2011 @ 02:56 PM
- State changed from “new” to “needs_verification”
(from [64b9a578975a52f4f96a6461ae3fe99f5ff8ab14]) Use node context for job reference arg expansion
[#426 state:needs_verification] https://github.com/dtolabs/rundeck/commit/64b9a578975a52f4f96a6461a...
-
Greg Schueler October 25th, 2011 @ 10:20 AM
- Assigned user set to “Greg Schueler”
- State changed from “needs_verification” to “resolved”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
(DEPRECATED) Please use github issues for issue tracking at http://github.com/dtolabs/rundeck/issues
Greg Schueler
Matt