![SAS rPath [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_100/s4j7v9akvsx7bcs3dbdp47h28tft.jpg?_a=BACAGSGT)
![UrbanCode Deploy vs SAS rPath [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_30/vrgt1zpi8gqi3wy9lt9smu963yx9.jpg?_a=BACAGSGT){kind=small}
rBuilder Packaging and Automation
Be sure of what you want before implementation as it can be costly to correct a mistake.
What is most valuable?
How has it helped my organization?
I Integrated rBuilder with Jenkins and setup a Continuous Deployment
What needs improvement?
API, deployment options, and the documentation.
For how long have I used the solution?
2.5 years
What was my experience with deployment of the solution?
Yes, as did not support platforms like ubuntu.
What do I think about the stability of the solution?
No issues encountered
What do I think about the scalability of the solution?
We did not test scalability
How are customer service and technical support?
Customer Service:
Customer Service was poor
Technical Support:Only a few people actually had in-depth knowledge
Which solution did I use previously and why did I switch?
This was the first solution we used, and then we switched to our home made Jenkins/RPM Solution.
How was the initial setup?
I did not do the initial set-up, but it was not too complex.
What about the implementation team?
In-house
What was our ROI?
We didn't calculate it.
What's my experience with pricing, setup cost, and licensing?
I personally, did not do the pricing.
Which other solutions did I evaluate?
I did not do the evaluating, my manager did.
What other advice do I have?
Be sure of what your requirements are and will be in the future, as you might get stuck with a lot of development costs.
