Frontend:
Staging | PR - TEST on Jenkins |
|---|---|
go to dev/ front | go to dev/ front |
git checkout BRANCHNAME | GIT pull |
yarn install | yarn install |
yarn serve | git push origin BRANCHNAME:test2 |
check: LocalHost/ test1,2,3,4 | check: https://ci.gke.monsido.com/blue/organizations/jenkins/Monsido%20frontend/detail/test2/82/pipeline |
Note: if there is an error on yarn install then should run:
ssh-agent -s ssh-add ~/.ssh/id_rsa
Page Assist:
Staging |
|---|
go to dev/ page assist |
git checkout BRANCHNAME |
yarn install |
yarn build |
yarn start:watch |
check: LocalHost/ test1,2,3,4 |
Chrome Extension:
Staging |
|---|
go to dev/ Chrome Extension |
git checkout BRANCHNAME |
yarn install |
yarn serve (b:s) |
check: LocalHost/ test1,2,3,4 |
Staging vs PR:
open PR can be tested locally or deployed to test environment. This means that wont be able to see the change in staging.
yarn install yarn build or serve always locally.
git push origin to test on test environments (test2,3,4,5) - i.e - https://test2.staging.monsido.com/
When PR is in Master
Staging |
|---|
In the folder (Frontend) - git checkout master |
git pull |
git checkout BranchName (i.e - |
yarn install |
yarn serve |
check: LocalHost/ test1,2,3,4 i.e - http://localhost:3001/1/domains/5340/page-performance/pages |
Firefox Extension:
In the terminal do the following for Firefox;
git checkout master for instance
git pull
yarn install
yarn b:s:f (f is for firefox )
Then access the Debug add-ons (first screenshot)
Click on Load Temporary Add-on (second screenshot )
Select the manifest.json file from the dist-firefox folder (second last file in the folder)
Disable from the extension
The extension without (staging) is production I just don’t have it added in that screenshot only staging.
EXTRA:
yarn: command not found
install npm install --global yarn
yarn install