Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IaaS automation deployment not triggered and keep failing #9437

Closed
ss-dimasm opened this issue Jul 12, 2023 · 2 comments
Closed

IaaS automation deployment not triggered and keep failing #9437

ss-dimasm opened this issue Jul 12, 2023 · 2 comments
Assignees
Labels
added-late An issue that was added to sprint after it began back-end Relates to back end issues bug Something isn't working refinement To be included in a future refinement session

Comments

@ss-dimasm
Copy link

Describe the bug
the IaaS won't automatically run when we're have an updates based our deployment_branch and it will have "Queued" then "Failed" status after we click the DEPLOY button.

Expected behaviour
previously it's running smooth and work as expected, so it should same like the previous one.

Screenshots
image

Additional context
Payload that sent with POST method to single pipeline runner endpoint

{
    "id": "<SECRET>",
    "created": "2023-07-12T07:58:44.759Z",
    "modified": "2023-07-12T07:58:44.759Z",
    "buildStatus": "QUEUED",
    "S3Location": "<SECRET>",
    "pipeline": {
        "id": "<SECRET>",
        "created": "2023-05-17T05:30:41.577Z",
        "modified": "2023-07-12T07:58:44.000Z",
        "name": "Diary",
        "appType": "react",
        "buildCommand": "workspace @apps/diary build",
        "packageManager": "yarn-berry",
        "repository": "https://github.com/reapit/apps",
        "bitbucketClientId": "<SECRET>",
        "developerId": "<SECRET>",
        "outDir": "packages/diary/build",
        "clientId": "SBOX",
        "buildStatus": "FAILED",
        "subDomain": "<SECRET>",
        "appId": "<SECRET>",
        "installationId": "<SECRET>",
        "repositoryId": "<SECRET>",
        "branch": "main"
    },
    "codebuildId": null,
    "s3BuildLogsLocation": null,
    "type": "BUILD",
    "buildVersion": null,
    "currentlyDeployed": false
}
@ss-dimasm ss-dimasm added bug Something isn't working needs-triage labels Jul 12, 2023
@github-actions
Copy link
Contributor

Thank you for taking the time to report a bug. We prioritise bugs depending on the severity and implications, so please ensure that you have provided as much information as possible. If you haven’t already, it really helps us to investigate the bug you have reported if you provide ‘Steps to Replicate’ and any associated screenshots.
Please ensure any personal information from the production database is obscured when submitting screenshots.
This issue will be reviewed in our weekly refinement sessions and assigned to a specific project board. We may also update the ticket to request additional information, if required.
For more information on our processes, please click here

@AshDeeming AshDeeming added back-end Relates to back end issues and removed needs-triage labels Jul 12, 2023
@AshDeeming AshDeeming added the refinement To be included in a future refinement session label Jul 12, 2023
@bashleigh
Copy link
Contributor

#9405 duplicate

@bashleigh bashleigh added the added-late An issue that was added to sprint after it began label Jul 12, 2023
@bashleigh bashleigh self-assigned this Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
added-late An issue that was added to sprint after it began back-end Relates to back end issues bug Something isn't working refinement To be included in a future refinement session
Projects
None yet
Development

No branches or pull requests

3 participants