Try our new research platform with insights from 80,000+ expert users
SAS rPath [EOL] Logo

SAS rPath [EOL] Reviews

Vendor: SAS
2.5 out of 5
Leave a review

What is SAS rPath [EOL]?

rPath is specialized in automating the assembly, provisioning and updating of diverse operating systems and middleware platforms and application stacks throughout enterprises.
Get the Release Automation Buyer's Guide and find out what your peers are saying about SAS rPath [EOL] and more!
Buyer's Guide
Release Automation
March 2026
Get the category report
Helped 884,976 peers since 2012
 
 
Key learnings from peers
Last updated Mar 25, 2026

Valuable Features

  • "I integrated rBuilder with Jenkins and set up a Continuous Deployment."

Room for Improvement

  • "Customer Service was poor Technical Support: Only a few people actually had in-depth knowledge"
These insights are based on the in-depth reviews provided by peers to help you make a better buying decision.
Download our Release Automation Buyer's Guide for additional reliable information.

Learn more about SAS rPath [EOL]

SAS rPath [EOL] was previously known as rPath.

SAS rPath [EOL] customers

Kaiser Permanente, Local Government Federal Credit Union, Los Angeles County DPSS, Lotte.com Nantes University Hospital Center, National Bank of Greece, National Board of Social Services

Related questions

  • 28
When evaluating Release Automation, what aspect do you think is the most important to look for?
  • 20
What is the best suitable solution to deploy in Websphere 8.0?
  • 25
What are the must-have tools for CI/CD?
  • 54
What tips do you have for improving software release management processes?
  • 25
How to estimate whether using the AWS services is worthwhile for saving time and money for manufacturing at a retailer company?
  • 19
What are the main challenges of implementing a deployment pipeline?
  • 20
Why is Release Automation important for companies?

Product Categories

Product Categories
Release Automation
 
SAS rPath [EOL] Reviews Summary
Author infoRatingReview Summary
Senior Software Engineer at a pharma/biotech company with 1,001-5,000 employees2.5I used rBuilder for 2.5 years, appreciating its packaging and automation. While stable, it lacked Ubuntu support, had poor customer service, and needed API/documentation improvements. We eventually switched to a Jenkins/RPM solution due to these limitations.