We are thrilled to roll out the red carpet for our latest feature: Salto CI/CD for NetSuite.

NetSuite admins and developers are using different tools and methodologies which usually means they have very little visibility into each other’s work. This can create misalignment and potentially result in inconsistencies and errors in their system. Our new feature enables admins and developers to bring all NetSuite deployments, large and small, to one centralized pipeline—so they can see every single change across teams and environments, reduce errors, and release faster.

Salto CI/CD is designed specifically for organizations dealing with intricate NetSuite customizations or seeking more rigorous quality control and those who want to foster better collaboration between admins and developers.

But it's not just for the tech-savvy. If you want to manage NetSuite changes more efficiently but feel a bit daunted by the complexity of CI/CD (or maybe are not yet familiar with it at all), we’ve made it much easier to get started.

Let’s dive in.

Is there a disconnect?

We don’t have to tell you about the avalanche of business requests every NetSuite admin at a large organization receives daily. You do your best to deploy changes to your NetSuite environment while juggling the risk of errors and trying to keep track of every update.

This is a tall order, but the real challenge might be even bigger.

NetSuite admins are often disconnected from their developer counterparts who deploy to the very same environment. It's not just the workflows that are disjointed—at times there is no flow of information between the two teams around what’s being changed and when.

But what if we told you that building a centralized process together with your NetSuite developers could help you streamline your own deployments and reduce the risk of unexpected errors? Instead of working in silos and occasionally stepping on each other's toes, you could embrace collaboration for more productive work.

The answer is CI/CD.

Continuous Integration and Delivery (CI/CD) are tools and practices that provide developers with the means to automate portions of the development lifecycle. They are common practices in the larger software development world but still less common in the NetSuite space.

Salto is bringing CI/CD not only to NetSuite developers but to NetSuite admins, too.
‍

‍

Smoother collaboration and smarter deployments

Admins being disconnected from the development cycle is not a one-sided problem. On the other side of the fence, there’s a team of NetSuite developers working with SDF to deploy to the same environment. With advanced dev tools, their work is far more organized, but what they often lack is visibility into what admins are changing in production and staging. This creates the risk of smaller updates clashing with SuiteScripts and objects that developers are working on.

We’ve built our CI/CD solution to help teams centralize their pipeline for all deployments going into NetSuite, so they can track and manage them efficiently as well as capture all the changes from both admins and developers.

As an admin, you can automate various deployment tasks, including approvals, merging, testing, etc., using proven tools from the software development world. And the best part: you absolutely don’t have to be a coder to enjoy Salto CI/CD.

It's also important to note that NetSuite developers can continue using the same tools and processes they’re currently using (e.g., SDF, Git, CI tools) as Salto integrates with most of them.

‍

Salto CI/CD in action

What does this look like in practice? Let's review some real-world use cases.

‍

Once you connect Salto to your Git repository, it will generate a pull request (we’re using GitHub terms in our example but Salto integrates with all major Git services) for every deployment, which captures all of the planned configuration changes so your team can comment on, discuss, and approve them.
‍

‍
If your pull request doesn’t pass the relevant checks (e.g., due to a lack of approvals or failed automations), Salto will block the ability to deploy it to the target environment. Think of it as a virtual safety net, allowing you to catch potential issues before they affect your production environment.

Now, with a pull request attached to every deployment, you can connect your preferred CI tool in order to automate deployment tasks. This will allow you to implement various best practices for testing and validation without having to learn how to code or adopt complex dev tools.

You can also create Salto deployments from SDF pull requests and have a user-friendly diffs view, bridging the ‘format’ gap between developers working in SDF and Salto users.

With this update, our users gain access to a few more cool features. For example, restore previous configurations of your environment have become easier than ever. Salto now creates a snapshot of every successful deployment so you can revert to one of the past versions at any time.

You can also push selective deployments, similar to Git’s cherry-pick. If you have pending work in Salto that you don’t want to promote just yet, you can selectively pick and deploy individual changes from one environment to another.

All these new capabilities essentially enable you to work more efficiently and focus on what matters most—delivering high-quality results.

‍

Start your CI/CD journey today

Adopting new tech can feel like adding more work instead of reducing it, so we've made incorporating Salto CI/CD into admins’ and developers’ work as simple as possible. As long as you have access to a developer or a DevOps engineer who can help you set up a CI tool, you’ll be able to integrate it with Salto in a few easy steps.

We talk to NetSuite teams every day, and it’s amazing how much of an impact a strong collaboration culture can have on the efficiency of individual and team work as well as the overall atmosphere of a workplace. If you’re ready to take a closer look at how CI/CD can empower your team, reach out to us to learn how other NetSuite teams implement and use it with Salto.