We followed the instructions for starting a pipeline with the REST API and set an environment variable called "GUID". Our job's console output is
[cruise] setting environment variable 'GUID' to value '111111'
[cruise] overriding environment variable 'GUID' with value '2222222'
But when we use the REST API to get the job xml it is still set to the default value '111111', it does not seem to actually override the value?
When you schedule a pipeline through the REST API is there a better way to find that particular instance of the pipeline? Using an environment variable with a GUID value seemed to be the only way we could think to programmatically track the status?
The Continuous Delivery book talks about testers or other users promoting a build through a pipeline (instead of being triggered by a check-in and build process) and we were trying to do this programmatically through our own web application so we want to be able to start a pipeline and then update the web app with it's jobs status.
Any thoughts or suggestions?