Where is Application Repository stored?

[prashant_gadgil]

We are developing scoped applications in DEV instance and then using application repository to install them to higher environments.   In parallel, sys admin is periodically cloning lower environments from production for upgrade to London testing etc.  

My question is when he clones PROD into DEV, will my application repository be lost? which instance is application repository stored in? or is it stored in PROD instance ? or some other place internal to ServiceNow? 

So before he clones into DEV, should I be worried that my scoped applications in DEV will be lost? should I back them up into Source Control etc? What precautions should I take before DEV is cloned into and how do I recover my work after the clone is complete?

Any explanation of how app repository is stored will help.

Prashant

[ethanwallace]

Hey there,

Here is a link to the app repository:

https://apprepo.service-now.com/sn_appstore_store.do

And the documentation where I found it:

https://docs.servicenow.com/bundle/newyork-application-development/page/build/applications/task/t_Pu...

I'd be interested to hear what your team ended up doing after you made this post. Here's some background info on my experience so far (after I forgot to back it up to an update set before cloning):

Earlier today, my team cloned down to an instance we were using for app repo development and the result was bizarre. I expected to be able to tell it to install the latest version, but when I check My Company Applications, it isn't listed under "Installed" - only "In Development" and I can't find it anywhere else. It's now running the (outdated) production version of the app with no clear option to restore it.

Additionally, the sys_app entry is using the prod version, so I wasn't able to edit settings until I found an old backup from last year to override the record with. Even after that, I still don't have an option to restore and I'm thinking I might need to restore our instance from backup just to publish as an update set instead.

I've been struggling to dig up more information about the App Repository - it almost feels like a forgotten feature and, overall, it's been a huge disappointment. The app repo might only be helpful in a "versioning" capacity (even though restoring from backup is a pain as well). Going forward, I think my team will just stick to using update sets instead.