Gitlab flow solo (minimo)
-
Upload
viniciusban -
Category
Software
-
view
160 -
download
5
description
Transcript of Gitlab flow solo (minimo)
![Page 1: Gitlab flow solo (minimo)](https://reader031.fdocumentos.tips/reader031/viewer/2022013121/557c23d4d8b42aa77f8b4851/html5/thumbnails/1.jpg)
Gitlab flow solo (mínimo)
By @viniciusban Baseado em https://speakerdeck.com/ogom/gitlab-flow
![Page 2: Gitlab flow solo (minimo)](https://reader031.fdocumentos.tips/reader031/viewer/2022013121/557c23d4d8b42aa77f8b4851/html5/thumbnails/2.jpg)
Uma dica
use branches e tags
![Page 3: Gitlab flow solo (minimo)](https://reader031.fdocumentos.tips/reader031/viewer/2022013121/557c23d4d8b42aa77f8b4851/html5/thumbnails/3.jpg)
Observações
● Essa proposta de fluxo não é a ideal porque mexe direto no branch de produção.
● Se você trabalha sozinho, recomendo usar o gitlab flow solo.
![Page 4: Gitlab flow solo (minimo)](https://reader031.fdocumentos.tips/reader031/viewer/2022013121/557c23d4d8b42aa77f8b4851/html5/thumbnails/4.jpg)
Crie um projeto
master
![Page 5: Gitlab flow solo (minimo)](https://reader031.fdocumentos.tips/reader031/viewer/2022013121/557c23d4d8b42aa77f8b4851/html5/thumbnails/5.jpg)
Crie um feature branch
master
feature
Para cada funcionalidade que será desenvolvida
![Page 6: Gitlab flow solo (minimo)](https://reader031.fdocumentos.tips/reader031/viewer/2022013121/557c23d4d8b42aa77f8b4851/html5/thumbnails/6.jpg)
Faça commits
master
feature
Quantos forem necessários
![Page 7: Gitlab flow solo (minimo)](https://reader031.fdocumentos.tips/reader031/viewer/2022013121/557c23d4d8b42aa77f8b4851/html5/thumbnails/7.jpg)
Merge
master
feature
Integre com o MASTER
![Page 8: Gitlab flow solo (minimo)](https://reader031.fdocumentos.tips/reader031/viewer/2022013121/557c23d4d8b42aa77f8b4851/html5/thumbnails/8.jpg)
Deploy
master
feature
producao
Integre MASTER → PRODUCAO.Crie uma tag.Faça deploy.
v1.0
servidorweb
deploy
![Page 9: Gitlab flow solo (minimo)](https://reader031.fdocumentos.tips/reader031/viewer/2022013121/557c23d4d8b42aa77f8b4851/html5/thumbnails/9.jpg)
quando houver erro em produção...
![Page 10: Gitlab flow solo (minimo)](https://reader031.fdocumentos.tips/reader031/viewer/2022013121/557c23d4d8b42aa77f8b4851/html5/thumbnails/10.jpg)
Faça commits
master
producaov1.0
No branch PRODUCAO
![Page 11: Gitlab flow solo (minimo)](https://reader031.fdocumentos.tips/reader031/viewer/2022013121/557c23d4d8b42aa77f8b4851/html5/thumbnails/11.jpg)
Deploy
master
producao
Crie uma tag.Faça deploy.
v1.0 v1.0.1
servidorwebdeploy
![Page 12: Gitlab flow solo (minimo)](https://reader031.fdocumentos.tips/reader031/viewer/2022013121/557c23d4d8b42aa77f8b4851/html5/thumbnails/12.jpg)
antes de continuar nova feature...
![Page 13: Gitlab flow solo (minimo)](https://reader031.fdocumentos.tips/reader031/viewer/2022013121/557c23d4d8b42aa77f8b4851/html5/thumbnails/13.jpg)
Merge
master
producao
Integre PRODUCAO→ MASTER
v1.0 v1.0.1
![Page 14: Gitlab flow solo (minimo)](https://reader031.fdocumentos.tips/reader031/viewer/2022013121/557c23d4d8b42aa77f8b4851/html5/thumbnails/14.jpg)
Merge
master
producao
Integre CORRECAO→ MASTER
v1.0 v1.0.1
MASTER, agora, tem a mesma correção que PRODUCAO
![Page 15: Gitlab flow solo (minimo)](https://reader031.fdocumentos.tips/reader031/viewer/2022013121/557c23d4d8b42aa77f8b4851/html5/thumbnails/15.jpg)
Por que branches?
● Código antigo intacto até saber se novo desenvolvimento está certo
● Produção separada do desenvolvimento
![Page 16: Gitlab flow solo (minimo)](https://reader031.fdocumentos.tips/reader031/viewer/2022013121/557c23d4d8b42aa77f8b4851/html5/thumbnails/16.jpg)
Por que tags?
● Para voltar versão facilmente– Rapidez e simplicidade em caso de emergência