atlassian / atlassian/github-for-jira

Deployment status when using self hosted

Open
#1,945 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
No language data
Stars
655
Forks
194
PR merge metrics
No merged PRs in 30d

Description

Hi I am trying to integrate deployment status in Jira. I am using AWS CloudBuild and Zappa to deploy on Lambda. I am trying to run this workflow when pull request is merged into master.
This is the script I am using from deployment section:

```
name: Deploy

on: [push]

jobs:
deploy:
name: Deploy my app

runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v1

- uses: chrnorm/deployment-action@v2
name: Create GitHub deployment
id: deployment
with:
token: '${{ github.token }}'
environment-url: http://my-app-url.com
environment: production

- name: Deploy my app
run: |
# add your deployment code here

- name: Update deployment status (success)
if: success()
uses: chrnorm/deployment-status@v2
with:
token: '${{ github.token }}'
environment-url: ${{ steps.deployment.outputs.environment_url }}
deployment-id: ${{ steps.deployment.outputs.deployment_id }}
state: 'success'

- name: Update deployment status (failure)
if: failure()
uses: chrnorm/deployment-status@v2
with:
token: '${{ github.token }}'
environment-url: ${{ steps.deployment.outputs.environment_url }}
deployment-id: ${{ steps.deployment.outputs.deployment_id }}
state: 'failure'
```
I am not a able to see the deployment status even though I have configured everything correctly. Can anyone please guide me on this?

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the provided GitHub Actions workflow, especially the deployment-action and deployment-status steps, and compare it with the self-hosted AWS CloudBuild and Zappa setup. Determine where deployment status should appear in the Jira integration and what configuration or workflow evidence confirms success. The repository is marked deprecated and moved to a private repository, so the current public issue does not identify a practical completion path.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, github-actions
Domain
cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.