I don't know exactly what your question is but I'll try my best to answer.
Testing DI Studio Jobs
I shortly explained a while ago in this forum. Perhaps I'll outline it in How To and Best Practices Section.
Integration into a CI system.
SASUnit is desiogned to be called by a shell command. Any CI tools should be able to do that.
What Jenkins PlugIn does is, that you can manage multiple installations of SASUnit on your CI worker node.
For instance you can have numerous SASUnit versions alongside each other. If you want to verify that the new SASUnirt release produces the same results as the old one did.
Furthermore the plugIn creates the call to the shell command to call SASUnit. Jenkins plugIn does not do really much.
What you need to figure out is how Bamboo handels success or failure of a job. Jenkins uses a XML-file with JSON objects to determine the number of tests and failures.
How does Bamboo do it?
If you have questions about how to adopt Jenkins-JSON-file to your requirements just drop a post here.
Regards
Klaus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I want to use SASUnit to test DIS job.
However I want to integrate with Bamboo, in order to automate the tests.
Has anyone done anything like this?
I know there's an add-on for Jenkins, but in this project I'm not going to use Jenkins.
Thank you very much.
Good job
Hi Gustavo,
I don't know exactly what your question is but I'll try my best to answer.
Testing DI Studio Jobs
I shortly explained a while ago in this forum. Perhaps I'll outline it in How To and Best Practices Section.
Integration into a CI system.
SASUnit is desiogned to be called by a shell command. Any CI tools should be able to do that.
What Jenkins PlugIn does is, that you can manage multiple installations of SASUnit on your CI worker node.
For instance you can have numerous SASUnit versions alongside each other. If you want to verify that the new SASUnirt release produces the same results as the old one did.
Furthermore the plugIn creates the call to the shell command to call SASUnit. Jenkins plugIn does not do really much.
What you need to figure out is how Bamboo handels success or failure of a job. Jenkins uses a XML-file with JSON objects to determine the number of tests and failures.
How does Bamboo do it?
If you have questions about how to adopt Jenkins-JSON-file to your requirements just drop a post here.
Regards
Klaus
Thank you very much.
Good analysis and excellent response.
I'll look into how Bamboo determines the number of tests and failures.
Thanks
Regards
Gustavo
Last edit: Gu Gonçalves 2017-08-11
I saw now, that SASunit creates a junit.xml file and i can use junit parser to integrate with Bamboo.
Thanks Klaus.
Regards,
Gustavo