I second this. It would be really nice to see the actual build number
created in the response somewhere when using the api build and
buildWithParameters calls. We can try to figure it out based on the
nextBuildNumber, plus parsing through the queue/api/xml output, but it
is not guaranteed.
I cre
I have perl scripts that automate setting up and modifying our job
configurations using get/post to the api. But, have a few issues with
keeping the xml properly formatted using the perl XML::Simple module.
Does anyone have the proper settings for the XMLin and XMLout calls?
amples with Java/Groovy in the Wiki and in the web.
> Maybe a quick alternative to solve your issue.
>
>
> On Wed, Jun 27, 2012 at 9:44 PM, Jim Searle wrote:
>>
>> I have perl scripts that automate setting up and modifying our job
>> configurations using get/post
I have to do this with one of our processes as well, this is basically
what I do:
- The main job has 3 promotion criteria, RegressionsPassed,
ComparePassed, CompareApproved.
- The CompareApproved is a "manual" promotion
- This job triggers all the regressions
- Have a job called 'compare', whic
Thanks! I will look at XML::Twig
On Wed, Jun 27, 2012 at 5:29 PM, Mark Heiges wrote:
> Can you use XML::Twig? It works well for me to modify configurations through
> the api.
>
> On Jun 27, 2012, at 4:45 PM, Jim Searle wrote:
>
>> Thanks, and I agree, but I have very litt