In 2020, we started an initiative called Jira/Confluence Cloud First Releases for Ecosystem which enabled a developer to enroll their cloud instances to receive Atlassian’s latest cloud platform APIs, features, and changes.
We’re happy to announce that we’ve made improvements by branding this program as the Developer Canary Program and introducing two new apps (one for Jira and one for Confluence) that you can install on your test instances.
Those who submitted their cloud instances as part of Jira/Confluence Cloud First Releases initiative (via the Google Forms) will continue to be part of this program even if they don’t install these apps.
This program is part of our efforts to improve Partner Sentiment and Stability and Reliability with our Developer and Partner Community. For more details on our efforts on improving Ecosystem Platform and Marketplace Stability and Reliability, follow our updates here.
*Marketplace Partners with at least 1 paid-via-Atlassian app qualify for Partner Portal resources. If you experience any issues getting access, and meet the eligibility criteria, please open asupport ticketand our team will work to get things resolved as quickly as possible.
You can un-enroll and re-enroll the tenant in the DCP program if you wish to compare the behaviour of your app. When you un-enroll, the changes won’t be available to your tenant.
What happens to instances that were part of the earlier “Cloud First Releases initiative” and install this app as well? Will it still rollback the first-cohort features on those instances when deactivating the toggle in the app? Or are we still enrolled, no matter how the toggle is configured?
Also, is there any delay when unenrolling until the first-cohort features are being rolled back?
@BenRomberg This app uses the same cohort as the Cloud First Releases initiative. If you install the app on an instance that’s already enrolled, you will see the app’s toggle already enabled. You can turn off the toggle to unenroll your instance, or just use the app to keep track of which instances you enrolled.
As for a delay, you get unenrolled immediately, but how each feature responds depends on how it is engineered to read feature flags. Most of the time, you should see the change immediately. Unenrolling your instance has the same practical effect as if we had turned off the feature flag ourselves to conduct a rollback.
@huasoon It shouldn’t be a problem to install the app on an instance that’s already enrolled. The app is part of the very same program.
Please try again later, and if it still persists, let us know if you see any errors in the Network tab of your browser’s developer console. You may also be able to get it working on a new instance.
Can I ask for a feature of the app? The ability to quickly raise an issue from within the context of the Developer Canary instance. If we’re going to be canaries, we should also be able to sing from within our cage
