Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
How are people combining cloud with a gitflow workflow?
Say you have 2 envs
Dev and Live
You then work on feature branches that you merge into Dev... the client approves these and they need to get deployed to Live... but not the entire dev env can be deployed since it might contain changes that aren't approved yet...
Also with baseline in place... what happens if you also make a change to the base and then deploy that to the child (dev env) how can you then move those changes to live without deploying everything....
We could have this discussion internally. But maybe it's good to post my experiences here so other people can benefit as well.
Umbraco Cloud out of the box and git flow does not work well together in my opinion. This is because you work on repository that is hosted on cloud . The only way to sync code between developers is to push to cloud and the other developer pulls that code. And once it is on cloud it's there. So pushing it to live pushes everything.
So a more suitable workflow for cloud is using Github flow : https://guides.github.com/introduction/flow/
The idea here is that your branch is always production ready.
There is a way that you can roll out hotfixes to live : https://our.umbraco.com/documentation/Umbraco-Cloud/Deployment/Hotfixes/
But that is cumbersome approach.
All the above works fine when you don't have code that is hosted in your own repository. Like described here https://our.umbraco.com/documentation/Umbraco-Cloud/Set-Up/Working-With-Visual-Studio/#the-git-repositories
So if you follow that approach it makes even more difficult.
One approach that worked very well for me in the past is the one outlined here :https://shazwazza.com/post/web-application-projects-with-umbraco-cloud/
With this setup you have the entire cloud site in your own repository. And you don't need to push to cloud to sync code between developers.
A benefit of this approach is that you have everything in your own repo. Pushing to cloud is only done to deploy stuff.
Another benefit is that you can do pull request reviews, CI/CD, etc...
When working with larger teams this setup is what I would recommend.
The only thing that needs to be done manually is keep your own setup in line with the automated upgrades that happen on the cloud platform.
I heard some talks that cloud would support feature environments. So when you push a feature branch to cloud it would spin up a new temporary environment with the code of the feature branch.
But I don't know if that is still on the roadmap.
ok makes sense and how about a dev and live on cloud? So client van sign off on some or all changes before deploying these to live from dev (and not push everything from dev to live)
That is not possible. It is all or nothing. Means clients have to be educated about this as well.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted