Can a CICD spoke get implemented for App Repo without Source Control?

[Alireza3]

I would like to know if a CI/CD spoke can be configured and implemented for App Repository release automation without being integrated or linked to a Source Control system (e.g., GitHub, etc.). Has anyone here successfully implemented a CI/CD spoke/flow for App Repository automation with no link or integration to a Source Control system?

Specifically, can a version of the application be published from Dev and get installed directly from Dev to Test, for example, without being sent to and then retrieved from a Source Control tool? Personally, I have not found any documentation on ServiceNow providing guidelines for CI/CD spoke configuration where Source Control integration has been skipped.

Thank You!

[Maik Skoddow]

Hi @Alireza3 ,

Sure, it goes without saying that! 

I am very sure of this, because I have built my own comprehensive deployment pipeline solution that does exactly what you describe. Unfortunately, I can't simply make it available to you, but I have already written several articles about it: https://www.linkedin.com/pulse/servicenow-deployment-pipeline-part-1-motivation-purpose-skoddow-2ffk... 

Maik

[Alireza3]

Mike, Thanks for the reply. Though I could not find anything in four (4) parts of your article saying CICD spoke can be configured for release automation without Source Control involvement; actually couple of your diagrams have SC as an external system integrated to the solution. Please let me know if I missed anything.