Help with CI/CD Workflow for Sisense + GitHub Integration
Hi everyone,
We're currently using two environments—test and prod—and recently began using Sisense's Git integration with GitHub. We're now looking to improve our CI/CD process and wondering if anyone has come across solid documentation or examples.
Specifically, we're hoping to:
Automatically deploy changes from a feature branch in test to main in test after a pull request is merged
Then automatically deploy the same changes to prod
Has anyone implemented a workflow like this or found official guidance on automating these deployment steps? We'd love to avoid manually pulling these changes into each environment.
Appreciate any advice, links, or lessons learned!
Garrett Wolfe
Posted 1 year ago·Last reply 1 year ago
5 comments
DRay
·1 year agoGotcha, thank you.
I found a few posts that might help. Can you take a look and let me know if they provide the information you need?
Sisense-Git Integration Issues | Sisense Community
Dashboards as Code With Sisense Git Integration | Sisense Community
Best practises for co-dev in version control | Sisense Community
https://community.sisense.com/kb/sisense_administration/migrating-assets-across-environments-leveraging-git/22466
Garrett Wolfe
OP1 year agoHey DRay Dashboards and cubes
DRay
·1 year agoSo changes to Widgets and Dashboards? Or are you trying to update administrative settings or system updates/upgrades?
Garrett Wolfe
OP1 year agoDRay The changes that were merged into the main branch in test.
DRay
·1 year agoHi gwolfe,
What kind of changes are you wanting to pull into production?