| || |
[Help] Use Hudson as REST Client Testing
I would like to know if it possible to use Hudson as REST Client for web service?
Moreover, Is there any way to create a job that takes its input from the previous job results?
Think of Hudson as a scheduler. Hundson triggers tasks to run (generally build tasks) and publishes artifacts.
It is possible to create artifact dependencies between your tasks by publishing artifacts and having the downstream task consume that artifact. For example, you can say have each module on top of publishing their library or executable, also publish a folder with a text file with information on the module that just built. Then using a custom test runner in a downstream tasks, you can say consume these files you see from all the upstream tasks that have run tests that are tagged/categorized by those affected modules
Then I should take care about how the next job will take the value from the output of the previous one.
Do you know how to do so? I am using Curl with batch commands to test my stuff.
In the unix world, I believe you can use SED/AWK inside a shell script to process text using regular expressions and turn it into a piped output which saved into shell variables and then call curl using a shell script. I'm not too familair with this, I usually just end up writing Grunt tasks because that's what I know best.
Originally Posted by Xtremee
In windows, there are some powershell text utilities, but I'm not familair with that.
You can use parameterized build feature on jenkins to take the result from the current job and pass to the next.