SAS rPath [EOL] Review

Be sure of what you want before implementation as it can be costly to correct a mistake.

What is most valuable?

rBuilder Packaging and Automation

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?


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.

**Disclosure: I am a real user, and this review is based on my own experience and opinions.
Find out what your peers are saying about SAS, Broadcom, IBM and others in Release Automation. Updated: July 2021.
523,975 professionals have used our research since 2012.
Add a Comment
ITCS user