🚀 Automation Sauce - 🛍️MyAtlassianBag 🧪🌐 Product Development Cycle

Ammar Ahmed Butt

---

🚦Incident Management & 🏹 Customer Support

Jira Service Management & Jira Software

• Add Issue on Transition for Jira Cloud | Atlassian Marketplace - Free Tool

• As soon As a ticket is raised on the Service desk, it gets cloned in the software project.

• Issues are linked if the status of the issue is changed on the Software project, the status on the service project is changed as well, and an Email is sent to the End user at every stage automatically.

• Jira Ticket system 

---

🧪SQA - Automation (API) 

Postman & Github

• Back up your Postman collections to GitHub, a cloud-based hosting service for Git repositories, with the Postman to GitHub integration.

• Every change saved to your Postman Collection automatically commits changes to your GitHub repo in JSON format.

• GitHub | Postman Learning Center

• Postman

---

🧮 Tracking Progress

Jira and GitHub

• Connect your GitHub code with your project management in Jira. A separate Jira subscription is required. With two of your most essential tools connected, you'll spend less time managing projects and more time working on them. This integration is an open-source project, built and maintained by Atlassian.

• https://github.com/atlassian/github-for-jira

---

🚀 Build/Deployment Status

Jira Software - AWS - GitHub

• aws-samples/aws-codebuild-webhooks

• Creating a Jira Issues webhook

  • Follow Basic auth for REST APIs to obtain a basic auth header

Create a parameter in SSM containing the Jira Issues API endpoint for your Jira instance:

aws ssm put-parameter --cli-input-json 
'{ "Name": "/webhooks/jira-issues-webhook-url", 
"Value": "https://<my-jira-server>/rest/api/latest/issue/",
 "Type": "String", "Description": "Jira issues Rest API URL" }'

 Create a parameter in SSM containing your basic auth headers as a JSON string:

aws ssm put-parameter --cli-input-json 
'{ "Name": "/webhooks/jira-basic-auth-headers", "Value": 
"{\"Authorization\": \"Basic <base64 encoded useremail:api_token>\"}",
 "Type": "SecureString", "Description": 
"Jira basic auth headers for CodeBuild webhooks" }

Create an entry in the DDB webhooks table that uses the default template, substituting values as required:

 

aws dynamodb put-item --table-name CodeBuildWebhooks 
--item file://examples/jira.json

---

🚨Alerts - 👀Observability - 🎯Architecture 

• 🔥Firebase Performance Monitoring - helps you keep a close eye on your app as you roll out new features or make configuration changes.

• Firebase - A/B Testing.

• Firebase Integration with Jira, Slack, and Play Console

• Elastic.co APM observability Integration with Slack and Jira.

• Postman Monitors - Slack

• Onesignal - Integration with Google Analytics for Firebase

• Sentry integration with GitHub, Slack, and Jira.

• Compass | Mission control for your distributed architecture

---

📱CodeMagic CI/CD - Mobile App

• Fully hosted and managed CI/CD for mobile apps.

• Build automation with GitHub.

• Google Play Console - Publishing automatically on Play Store - We release it internally 1st.

• IOS - App Store Connect - Publish an App to TestFlight 1st.

• Integration with Slack

• Integration with Jira.

• Running test cases.

---

📊Google Analytics

• Integration with Firebase, Google Play Console, and Google Search Console.

• App Indexing on Google Search.

---

🗂️ Workflow - 1

• A branch is created on GitHub containing the Jira ticket ID i.e. “JIRA-00:”; automatically the ticket moves to "in progress" on the Jira Software board (In Progress is the ticket status). A comment is added on that Jira ticket with a time log as well, relevant users get tagged as well.
• The “start date” field is filled with the current date. (Jira issue/Story/Task/bug ticket)
• PR(Pull Request) is raised on GitHub, containing the Jira ticket ID i.e. “JIRA-00:”; Automatically the ticket moves to PR Review on the Jira board, Comment is added on that Jira ticket with a time log as well.
• Since the team lead is supposed to review the code, it automatically gets assigned to the lead, on the Jira board.
• PR(Pull Request) is Merged on GitHub Comment is added on that Jira ticket with a time log as well.
• Webhook Triggers (only on Three branches, develop, stage, master) AWS Codepipeline and the following process starts. E.g. Let's say if the branch is Develop to which PR is being Merged, and the ticket status changes to Deployed to develop on Jira

📌 AWS Code Pipeline Flow

• Source (GitHub - PR Merge)(Branch - Develop)
• Build
• Deploy
• Test

-- Postman - Newman (API testing)
-- Cypress

• If the pipeline ran successfully on AWS, a comment is added on that ticket which is on Jira Board, and that ticket is moved to Post Develop Testing ticket is assigned to the SQA, and manual testing is done.

• Now the flaw in this workflow is that it doesn't show or comment on the test results that ran in the pipeline on the Jira ticket, for I did find a solution, via APIs, and the test results are added on the Jira ticket in .xml format, but haven't been 100% successful yet. 💀

---

🗃️ Workflow - 2

• Everything remains the same till the PR merge and webhook trigger AWS Code Pipeline 

AWS pipeline flow

• Source (GitHub - PR Merge)(Branch - Develop)

• Build

• Deploy

• If the deployment was successful on AWS, a comment is added to that ticket which is on the Jira Board, and that ticket is moved to Deployed to Develop

• From Jira, a webhook is triggered, which will then create a monitor on the postman, run the test cases from the collection, and then send the summary of test cases in response to that webhook.

• The summary should get posted on that same Jira ticket, If 80% successful rate(which will be mentioned on the ticket) then the ticket transitions to "Post Develop QA", it gets assigned to the SQA, for further testing. (Trying to do this for the backend Deployment but haven't been 100% successful yet, for mobile apps using code magic, it was successful)💀

---

---

🧭 Workflow (Explained)

• The branch is created on GitHub containing the Jira ticket id i.e. “JIRA-00:”

  • Automatically the ticket moves to in progress on the Jira board

  • The “start date” field is filled with the current date.

• PR(Pull Request) is raised on GitHub, containing the Jira ticket id i.e. “JIRA-00:”.

  • Automatically the ticket moves to PR Review on the Jira board

  • Since the team lead is supposed to review the code, it automatically gets assigned to the lead, on the Jira board.

• PR(Pull Request) is Merged on GitHub

🧪 SQA - Automation 

• Postman

  • After deployment is done successfully, Test cases run in the pipeline, and the ticket is moved to

    • Post-Develop QA

    • Post-Stage QA

    • Post-Master QA

  • The ticket is automatically assigned to the QA Engineer.

  • Manual testing is done.

• Cypress Test cases with AWS Codebuild in Pipeline

---

 

Branch on GitHub	Status on Jira Board	AWS Pipeline - Triggers	Test Cases
Develop	Deployed to Develop	Source (GitHub - PR Merge)(Branch - Develop) Build Deploy Test Cases Postman Cypress	Environment BaseURL - Develop Test Cases will Run. Before the PR is Merged, if any new API is created, that is added to the Postman collection. Automatically it gets committed to the relevant branch.
Stage	Deployed to Stage	Source (GitHub - PR Merge)(Branch - Stage) Build Deploy Test Cases Postman Cypress	Environment BaseURL - Stage Test Cases will Run. Newman - Postman Cypress
Master	Deployed to Master	Source (GitHub - PR Merge)(Branch - Master) Build Deploy Test Cases Postman Cypress	Environment BaseURL - Master Test Cases will Run. Newman - Postman Cypress

---

📝 Release Notes - Organisation Updates

• Atlas | Your company’s new teamwork directory | Atlassian

• “Fix version”

  • Releases are created from the left side panel of the Jira board.

  • A manual trigger is added, and when triggered, it fills all the “fix Version” fields of all the closed tickets with the last unreleased version.

  • Automatically Release Notes are generated, one can copy and paste them all on Atlas Project.

  • All the subscribers will be notified.

  • Create Release Notes - Naming convention for Sprint Versions 

---

For more information check this Link -Processes & Standards

 

#AtlassianCreator #devops-story #MyAtlassianBag #AutomationSauce

Matthias Gaiser _K15t_

Hey @Ammar Ahmed Butt

this article looks like a quite comprehensive list, but I'm missing some context, maybe a primer in the beginning. Can you share a bit what this list is aiming to do? Are these your recommendations for automating things in the product life cycle?

Thank you,
Matthias.