Ordoline – Project Passport

Ordoline / UAB Sosterus

DELIVERED

–

WP

–

–

–

Timedoctor – ordoline

Monthly

Anna Potiiuk

UAB Sosterus

Oleksii Panchenko

Viktoriia Malysh

https://www.figma.com/file/HJv1uDtr5empwrTDD2dCNE/Ordoline?node-id=8928%3A13284&t=NbTCs0jXvXGk3yYn-0

There are several sites for different languages, the access to each is provided here – https://docs.google.com/spreadsheets/d/1RKjo5fsOGc8iZdC6p-cfYLHIQ7WxjyEEu2O0bmA0xec/edit?usp=sharing

1. create branch from master branch. But it depends because some websites has own branch like .com has COM branch .co.uk has UK branch. If some website needed any specific changes/features I usually created separate branch for that website. After I made changes I merge into DEV branch or depending on website to that website dev branch for example UK-DEV. After its approved I merged new task (from task branch not DEV branch) to master branch or to specific website branch.

2. and after that run pipeline to upload changes to live. Because if you do changes via FTP only those changes will be overwritten by pipeline.

3. But this workflow has same cons. If there is change that need to be on several website only for example .ee, .lv and .com . Then you need to create separate branches for those websites if they dont have. And then create 3 branches task branches for each. So it’s kinda time consuming depending how big task and if changes are on file that is already different in all websites for example if you need change home page but it has different section across those websites. So you cant create one branch and merge into separate website.

And if you create new branch for website language create Dev branch also for that language and never merge dev to prod branch because usually dev has several on going tasks.

in .gitlab-ci.yml file you need to changes these things – https://prnt.sc/i99b0EAmH6xe