Deployment not triggering after code push in Adobe Commerce Cloud
Code pushes to the staging or production branches via the GitHub or Bitbucket integration are not triggering deployments in Adobe Commerce Cloud as expected. To fix this, verify deployment permissions, check pipeline logs, validate branch configurations, and confirm repository integration using Cloud CLI.
Description description
Environment
Adobe Commerce Cloud
Issue/Symptoms
- Deployments fail to trigger after pushing changes from GitHub or Bitbucket to staging or production branches.
- The last successful deployment occurs several days ago.
- No modifications to project settings are reported prior to the issue occurring.
Resolution resolution
To resolve this issue, follow these steps:
-
Verify that no changes were made to deployment permissions or configurations in the project settings.
-
Check deployment pipeline logs for errors that prevent triggering.
-
Ensure that all required branch configurations (for example, staging/production) are correctly set up and aligned with the expected workflow for automatic deployments.
-
Confirm that there are no connectivity issues between the repository and the Adobe Commerce Cloud environment.
-
Use Cloud CLI to obtain the Integration ID for your GitHub or Bitbucket integration.
code language-none $ magento-cloud integration:list ... $integrationID github Repository: XYZ ... -
If there is an error when validating the integration with this command, such as Unable to connect to GitHub: repository not found, try to add the integration again:
$ magento-cloud integration:validate $integrationID
-
If the issue persists, contact Adobe Commerce Technical Support for further investigation.