Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The checklist has to be filled before and submitted as part of the approval process for the Add-on.

Technical readiness Checklist

View file
nameAtlassian Data Center app readiness checklist - Google Forms.pdf
height250

...

Step 2: Test your app and document the results

Completed the performance and scale testing of your add-on as listed below:

  • Detail your application testing for the deployment of your application in multiple Data Center nodes,
  • Detail the validation steps you take to ensure data is consistent in your application across multiple Data Center nodes,
  • Detail your application testing for the installation and upgrade of your application in a mutli node Data Center deployment, and
  • Detail any user testing steps you take to ensure features work in standard Data Center multi node deployment (such as our AWS deployments).

For Enhanced User profile the Testing was done on the AWS. The Jira data-center was deployed and tested with various nodes (1, 2 & 4) for the below actions. The test results are noted for the below scenarios

  1. Performance and Scale test results without Add-on for 1 node.
  2. Performance and Scale test results with Add-on for 1 node.
  3. Performance and Scale test results with Add-on for 2 nodes.
  4. Performance and Scale test results with Add-on for 4 nodes.

Step 3: Provide support escalation details

To facilitate quick resolution to any issues or impacts on the App, Atlassain recommends below activities (Service desk portal and responsible contact person).  

  • a clear escalation process for your customers available to Data Center licensed apps,
  • defining a single point of contact (which can be a mailing list) to raise escalations with,
  • to maintain the owner of the app contact in the DCHELP ticket, and
  • letting Atlassain know if you have an SLA with customers on Data Center licensed apps

Step 4: Create your Marketplace submission

Once steps 1-3 are completed and the approval on the technical review of your app is received, we can submit the app to Marketplace. Before uploading the Add-on in Marketplace we have the add the Data-Center compatibility descriptor in the Add-on as shown below.

Add Data Center compatibility to your add-on descriptor

<param name="atlassian-data-center-status">compatible</param> <param name="atlassian-data-center-compatible">true</param>

  • The atlassian-data-center-status parameter indicates to Marketplace and UPM that your app has been submitted for technical review according to these Data Center requirements.

  • The atlassian-data-center-compatible parameter was previously used to indicate Data Center compatibility and should be included for backward compatibility with older UPM versions


Here’s an example of a generic plugin-info block with these parameters:

<plugin-info>
    <description>${project.description}</description>
    <version>${project.version}</version>
    <vendor name="${project.organization.name}" url="${project.organization.url}" />
    <param name="atlassian-data-center-status">compatible</param>
    <param name="atlassian-data-center-compatible">true</param>
</plugin-info>
Note:
If the app is an OBR artifact with bundled dependencies, the above parameters should be included in both the main app descriptor as well as the descriptors for any dependencies.

Tools used:

  • J-Meter tool is used in automating the performance and scaling tests. The scripts and the actions included in the tests are listed below.
  • AWS Jira data-center is used  as the infrastructure to carryout the testing of the Add-ons. The template used is attached. The template has been modified so the template works on n-Virginia AWS region.

Timing Plan for Enhanced User profile Add-on Testing:

...