Coming soon: Your SAS software, continuously updated

2

Calling all SAS Administrators! Find support all in one place.

If you're my kids, the term, “continuous integration,” might have you thinking about how much time you’ve spent lately with the family, and “continuous delivery” is what's been happening on the front porch the past few weeks. But to a software developer, these terms mean something entirely different. Combined and abbreviated as CI/CD, the term refers to a powerful way to develop, test and deliver software.

What exactly is CI/CD?

CI/CD is the practice of continuously integrating and testing code, followed by the continuous delivery of that code to the target. In simple terms, it’s the process of constantly updating and validating software so that it can be rolled into production systems as quickly as possible.

And it’s how we’re going to begin releasing SAS Viya, SAS’ cloud-enabled, in-memory analytics engine.

A new way to deliver SAS software

Instead of delivering SAS Viya in major ship events that can create a delay between the time the developer adds the feature and when it can be used, or require down time while the update is installed, you’ll now be able to get SAS Viya updates and new features right away with automated delivery and installation, and minimal disruption to your work. The update would not be a wholesale change to every bit and byte of the software, but would instead run against a microservices-based containerized architecture orchestrated by Kubernetes, so changes would be incremental. The benefits? Limited downtime, and unlimited enhancements.

That’s what CI/CD promises to deliver, and I’m excited that the next release of SAS Viya will adopt this practice. In addition, our customers will be able to select the release intervals that align to their organization’s standards and policies. Those looking to stay on the cutting edge could pick monthly updates, whereas regulated or more conservative organizations could update every six months. The new software update method will also allow SAS Cloud customers to simply experience the latest and greatest from SAS without a bunch of manual intervention.

Helping you innovate faster

We understand that the changing needs of our customers require constant innovation, and this new approach will let us bring our innovations to your data scientists, business analysts and application developers, quickly so that our customers can continue to bring their innovations to the world.

Stay tuned for more technical details on release version methods, cycles, support policies and delivery mechanisms.

Learn more at www.sas.com/viya.

Share

About Author

Keith Renison

Principal Product Marketing Manager

Keith Renison is Principal Product Marketing Manager for cloud technologies at SAS. His background includes a variety of technical areas including data management, enterprise architecture, Hadoop, sustainability, profitability modeling, and visual analytics. Previous roles include program management, sales enablement, and technical support/delivery. Prior to joining SAS, Keith was a systems and database administrator in the telecommunications industry, and holds a bachelor's degree in Business Management and Organizational Leadership from George Fox University. Keith is a creative thinker, has a passion for precision, and a healthy respect for the power of words.

2 Comments

  1. May I know when we will get more information on ci/cd in sas viya, as recently I implemented devappa i.e Jenkin with gud lab on sas viya for ci/cd and it's working awesome..

    But I will be in sas admin role and looking for an update on ci/cd on sas viya for sas updated hot fixes etc.

    If possible can you send me some notes in this or any usefull links.

    • Keith Renison

      Thanks Shuva for your interest! The first release of SAS Viya in a CI/CD cadence is not yet generally available (GA), but is coming soon. Once it’s released, there will be ample documentation on how to deploy and manage CI/CD updates. Keep a watch on the sas.com/viya page for announcements on when it becomes GA!

Back to Top