Atlassian Connect / Cloud App versioning & best practices

atlassian-connect
jira-server
jira-cloud

#1

Is there a guide to versioning Atlassian Connect applications, specifically related to testing upcoming versions with a limited audience?

In our case, we’ll be serving up our application descriptor at example.com/jira/connect
I noticed that in the Marketplace Admin, I am able to create a new version. One of the options is to add a URL.

It seems that I could use an alternate or “pre-production” URL here, i.e. testing.example.com/jira/connect and create a new version of the application that could be used for testing as a private app. Then, when testing is completed, we roll out the new version at the “production” url, i.e. example.com/jira/connect.

Is that an intended use of this feature of the Marketplace?

Any advice on versioning/upgrades appreciated. I have read through https://developer.atlassian.com/platform/marketplace/upgrading-and-versioning-cloud-apps/ but am looking more for best practices on how to test upcoming versions and changes to a Connect app.