CI/CD (continuous integration/continuous delivery) is used heavily in professional application development these days, but there is no such thing in ServiceNow out-of-the-box.

The difference between 'classic' software development and the way it works in ServiceNow is how changes are captured. In ServiceNow that's the job of an 'update set' or a 'scoped application' - the others just use GIT for that.

So how difficult must it be to extract all code inside an 'update set' into a GIT repo and send it to a CICD pipeline?

Actually not very....

Over the last year I have developed an open source CICD server for ServiceNow to allow to send update-sets or applications through a CICD pipeline with standard tools.

It automates code quality checks, code documentation, ATF test execution and deployment. Just these tings you need to to have to bring transparency in place.

Here is an example implementation of it which works with GitHub

https://github.com/bmoers/sn-cicd-example-v3

The core project can be found here

https://github.com/bmoers/sn-cicd