Versions Compared

Version Old Version 21 New Version 22
Changes made by

YUVARAJ KUNDASI (Unlicensed)

YUVARAJ KUNDASI (Unlicensed)

Saved on

Key

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

Table of Contents

Objective:

Get approval from Atlassain for submitting the Add-on as Data-center approved in the Atlassain marketplace. 

Introduction:

Atlassian has introduced new requirements for vendors who want to publish Data Center approved apps in Atlassian Marketplace. In order to get the Add-on approved on the Atlassain Marketplace, the below tasks has to be completed:

  1. Complete a technical readiness checklist
  2. Test your app and document the results
  3. Provide support escalation details
  4. Create your Marketplace submission

Test Implementation Steps:

Step1 : Complete a technical readiness checklist

...

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

...

<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.

...

View file
namequickstart-vpc-for-atlassian-services.yaml
height150

Timing Plan for Enhanced User profile Add-on Testing:


TasksActivityResponsibility Estimation in hrsStart dateEnd DateStatusComments
1Install Jira Data-center for validating the Add-on. Local Environment




This is required to show to JIRA assessment team
1.1Pre-requisites

Mar-4-2019Mar-6-2019

1.1.1Node-1,2 and3 with Jira installationYUVARAJ KUNDASI (Unlicensed)3

Status
colourGreen
titleCompleted

1.1.2Load BalancerYUVARAJ KUNDASI (Unlicensed)3

Status
colourGreen
titleCompleted

1.1.3Jira DBYUVARAJ KUNDASI (Unlicensed)3

Status
colourGreen
titleCompleted

1.1.4JIRA Instance(Application and Application media storage)YUVARAJ KUNDASI (Unlicensed)3

Status
colourGreen
titleCompleted

1.2Test  app and document the results as defined in the readiness document.   Mar-8-2019Mar-15-2019
Attachment link : https://developer.atlassian.com/platform/marketplace/dc-apps-submitting-your-app/
1.2.1Complete Performance and Scale testing




Ref link: https://developer.atlassian.com/platform/marketplace/dc-apps-performance-and-scale-testing/
1.2.1.1

Create User Actions list for the performance testing.

Automate the tests using Jmeter

Dipesh Chouksey (Unlicensed)4

Status
colourYellow
titleIn Progress

Automated testing scripts for testing the Add-on on data-center.

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6f8446ac-0270-38e8-bfda-78a5daa9d08d
keyAP-238

Test data for Jira instance.xlsx

1.2.1.2Deploy 1 nodes data center with data.YUVARAJ KUNDASI (Unlicensed)2

Status
titleTo do
To be deployed just before testing to save costs.
1.2.1.3Perform and Capture results for the performance actions with and without Add-on scenariosDeepthi Reddy N B (Unlicensed)12

Status
titleTo do

1.2.2Scale testing steps & MethodYUVARAJ KUNDASI (Unlicensed)2

Status
colourGreen
titleCompleted
Performance testing steps for different deployments (1, 2 & 4 ) nodes
1.2.2.1Deploy 1 Node data center with data.
4

Status
titleTo do
To be deployed just before testing to save costs.

1.2.2.2

Test User Actions list for the performance testing for 1 node
4

Status
titleTo do

1.2.2.3

Deploy 2 Node data center with data.
4

Status
titleTo do
To be deployed just before testing to save costs.
1.2.2.4Test User Actions list for the performance testing for 2 node
4

Status
titleTo do

1.2.2.5Deploy 4 Node data center with data.
4

Status
titleTo do
To be deployed just before testing to save costs.
1.2.2.6Test User Actions list for the performance testing for 4 node
4

Status
titleTo do

2Provide support escalation details to Atlassian for Data Center Compatibility  Mar-18-2019Mar-18-2019

2.1Create a clear escalation process for your customers available to Data Center licensed apps
1

Status
titleTo do

2.1Define single point of contact (which can be a mailing list) to raise escalations with
1

Status
titleTo do

2.1Create and maintain the owner of the app contact in the DCHELP ticket
1

Status
titleTo do

2.1Create and communicate Atlassian about SLA with customers on Data Center licensed apps
1

Status
titleTo do

3Complete technical review with Atlassian after submitting the readiness document. Atlassian & Empyra40Mar-19-2019Mar-25-2019
Status
titleTo do
Dependency with Atlassian
4Contingency plan for App changes & review with AtlassainAtlassian & Empyra40Mar-26-2019Apr-2-2019
Status
titleTo do
 
5Add Data Center compatibility to your app descriptor Dipesh Chouksey (Unlicensed)2Apr-3-2019Apr-3-2019
Status
titleTo do
 
6Upload App to MarketplaceKarthikh Pandian
2Apr-3-2019Apr-3-2019
Status
titleTo do



Total hours144



Reference links: