Known Limitations and Considerations

As we continue to gather insights from our users, there are some known limitations and considerations to be aware of.

Potential Limitations and Considerations

Format Restrictions

• The packaged artifact from your CI/CD pipeline must adhere to the Umbraco Cloud API's required format, which is a zip source file. This could necessitate changes to your existing build and packaging scripts.

Back Office Limitations

• To ensure smooth execution of the Umbraco CI/CD Flow, it is highly recommended to adhere to a specific principle: refrain from making any alterations to the schema, except in the leftmost environment within the Umbraco Cloud back offices. The intention behind this principle is to prevent conflicts that could potentially arise due to simultaneous modifications made in different environments.

Additional Build Step

• The flow feature adds an extra build to the deployment process. As a result, it takes longer to post to Umbraco Cloud using Umbraco CI/CD Flow compared to standard deployments.

Conflict Management

• Given the necessity to avoid changes in other environments, the lack of strict coordination among multiple teams or individuals working on the same project elevates the risk of conflicts.

Key Points to Consider

• Direct Commits to Umbraco Git Repos: Any commits made directly to the Umbraco-git-repos will cause the process to fail.

• Remote Build/Test Options: It is currently not possible to skip the first build step before committing.

• Incomplete API:

  • The list endpoint lacks filtering capabilities.

  • The promotion endpoint for transitioning from dev to stage to live is not fully functional yet.

• Hotfix Deployments: Direct deployments to a specific environment are not supported at this time.

• Lack of Predefined Tasks: There are no Umbraco-provided Azure DevOps tasks or GitHub Actions available.

• No Webhooks: Currently, there's no webhook support for real-time feedback to the pipeline; polling is the only option.

• Casing Conflicts: Be cautious of casing issues, such as having a README.md file created by Azure DevOps and a Readme.md file from the default Umbraco Cloud, as this can cause conflicts in the cloud Git repository.

• Documentation Alignment: We are in the process of updating our documentation to align with standard Umbraco guidelines.

• Developer Experience: Plans are underway to create Umbraco-specific Azure DevOps tasks and GitHub Actions to enhance the developer experience.

Contact Information

For any queries, comments, or further clarifications, feel free to reach out to us at Umbraco via email at [e-mail].