Did anyone try that feature and has some feedback? Or Does anyone know some useful samples to look up?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Did anyone try that feature and has some feedback? Or Does anyone know some useful samples to look up?
I have tried this feature some months ago, but I don’t use it anymore (just because I don’t need it, not because it is not a good feature).
Basically, you define n Axis, each axis is a property with several values.
Let’s go with an example: you define the Axis ‘JDK’, with possible value ‘1.4’, ‘1.5’, ‘1.6’, and you define another property ‘database’, where possible values are ‘oracle’, ‘mysql’.
Thus, Hudson will launch your build 6 times:
Then, once everything is finished, you will be able to see the results for each iteration.
This feature may be really usefull when you need to test your application in several environments (in my example, with different versions of JDK or database).
Note that except for the JDK axis, you have to manage by yourself the property given as entry by Hudson. In my example, the application must take into account the ‘database’ property itself. Eventually, a good idea is to use this property to enable a particular profile in the Maven2 configuration, if you project is mavenized (see here for more details about that).
I hope my explanations are clear enough 🙂