I have integrated SASUnit in my SAS9.4 linux server and I am planning to integrate it into Jenkins. Since I dont have admin access to Jenkins, i am gathering details on the SASUnit plugin. Here are some of my questions at this point:
1. Can the HTML reports generated in ../doc/rep get displayed in Jenkins?
2. Can the build status be configured based on number of acceptable errors/warnings in the unit tests?
Is it possible to share some screen shots from Jenkins with the SASUnit plugin features?
Thanks in advance,
Dilip
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
first of all some short answers to your questions:
1. Yes, you can use a post build step called "Publish HTML Report"
2. Yes to some extend. SASUnit can create a JUNIT.xml-file. If there are any failed asserts the build will be unstable. The contents of the JUNIT-file will be displayed in Jenkins.As far as I know you can define a threshold to say three fialed asserts shall be stable. Four and more are unstable.
I will share screenshots to all questions and gather some information on what SASUnit-PlugIn is build and used for.
Due to the fact that these answers will be a bit lengthy, I decided to publish them in the SASUnit Documentation in the Best Practices Section.
This information will be helpfuk for others too.
Just give me a bit time to aggregate and refine the information.
I will post you reminder here when I#m finished.
Regards
Klaus Landwich
Last edit: Klaus Landwich 2017-05-11
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks! I am going through it and hopefully will be able to install the plugin in some days.
In my case, Jenkins and SAS are in different servers. So, I assume I have to ftp the log+rep directories to the Jenkins.server for the plugin to pick it up. Correct?
Thanks,
Dilip
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You could try to add your SAS machine in Jenkins as a node (aka slave). In Jenkins that's pretty simple. If you bind your job to the SAS node it will run there and Jenkins gathers all information on the node, not the master.
So there would be no need to ftp any files from SAS to Jenkins.
I do not know if Jenkins requires admin rights on the nodes.
That's the way we do it with SASUnit in our Jenkins. We have three separate nodes (SUSE Linux, Ubuntu Linux and an English Windows).
Regards
Klaus
Last edit: Klaus Landwich 2017-06-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was not able to set up SAS server as a slave node and hence SASUnit plugin was not usable, but HTML Reports Publisher plugin did the trick. I have some more missing pieces before my Continous Integration pipeline is completely set up.
Thanks,
Dilip
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hi,
I have integrated SASUnit in my SAS9.4 linux server and I am planning to integrate it into Jenkins. Since I dont have admin access to Jenkins, i am gathering details on the SASUnit plugin. Here are some of my questions at this point:
1. Can the HTML reports generated in ../doc/rep get displayed in Jenkins?
2. Can the build status be configured based on number of acceptable errors/warnings in the unit tests?
Is it possible to share some screen shots from Jenkins with the SASUnit plugin features?
Thanks in advance,
Dilip
Hi Dilip,
first of all some short answers to your questions:
1. Yes, you can use a post build step called "Publish HTML Report"
2. Yes to some extend. SASUnit can create a JUNIT.xml-file. If there are any failed asserts the build will be unstable. The contents of the JUNIT-file will be displayed in Jenkins.As far as I know you can define a threshold to say three fialed asserts shall be stable. Four and more are unstable.
I will share screenshots to all questions and gather some information on what SASUnit-PlugIn is build and used for.
Due to the fact that these answers will be a bit lengthy, I decided to publish them in the SASUnit Documentation in the Best Practices Section.
This information will be helpfuk for others too.
Just give me a bit time to aggregate and refine the information.
I will post you reminder here when I#m finished.
Regards
Klaus Landwich
Last edit: Klaus Landwich 2017-05-11
Hi Klaus,
Thanks for the answers and I am looking forward to seeing your signal once you are done with the documentation.
Thanks,
Dilip
Hi Dilip,
the new documentation for SASUnit and Jenkins is alive now.
You can find it in the documentation section:
Documentation > User's Guide > How to and Best Practices.
Here's the link: How to and Best Practices
If you hav any questions, comments or enhancements just let me know.
Regards
Klaus
Hi Klaus,
Thanks! I am going through it and hopefully will be able to install the plugin in some days.
In my case, Jenkins and SAS are in different servers. So, I assume I have to ftp the log+rep directories to the Jenkins.server for the plugin to pick it up. Correct?
Thanks,
Dilip
Hi Dilip,
You could try to add your SAS machine in Jenkins as a node (aka slave). In Jenkins that's pretty simple. If you bind your job to the SAS node it will run there and Jenkins gathers all information on the node, not the master.
So there would be no need to ftp any files from SAS to Jenkins.
I do not know if Jenkins requires admin rights on the nodes.
That's the way we do it with SASUnit in our Jenkins. We have three separate nodes (SUSE Linux, Ubuntu Linux and an English Windows).
Regards
Klaus
Last edit: Klaus Landwich 2017-06-21
Hi Klaus,
Documention helped a lot. Thanks so much.
I was not able to set up SAS server as a slave node and hence SASUnit plugin was not usable, but HTML Reports Publisher plugin did the trick. I have some more missing pieces before my Continous Integration pipeline is completely set up.
Thanks,
Dilip