cross-posting!

I found this forum to be really helpful in tips/tricks on the CI/CD process. We have heavy use of Restlets (and custom records/fields etc), and I’m in the process of putting all that code into a repo with our main service app. I’m trying to get to a state where my QA/PM team knows, via our work item system (Azure devops), that our netsuite environment has changed (via PRs) and can determine the need/scope of re-testing. Just truth in sales, I’m a .net developer, this is my first experience with Netsuite.

Azure DevOps is a fantastic tool - I use it for home projects! Would be really good to see how successful "CI/CD"ing your NS pipeline is. I had read we may be stuck with a mono repo and be forced to deploy the whole project

It’s a project in-flight for sure. I like the ease at which I can bind any/all projects of a mono-repo to a specific commit/version of the code- one artifact that contains everything. I’ve got a little sample repo that I made when I started working on this project as a POC to deploy multiple (small) SDF account customization packages, it’s got some dependencies on environment vars in the devops pipeline (secrets/key for netsuite CLI). Let me see if i can scrub some of the organization specific code and put it in a git repo for ya (it’s in devops now for my employer)