feat: use two deploy branches for CI builds

This commit is contained in:
Siddarth Kumar
2024-07-17 09:14:34 +05:30
parent 93cac6adb9
commit bbe62ed384
2 changed files with 25 additions and 24 deletions

View File

@@ -8,10 +8,14 @@ To publish in the blog, create a `.md` or `mdx` file within the `rlog` directory
Please follow [sembr](https://sembr.org/) in the `.md` or `.mdx` file.
You can use [Frontmatter](https://docusaurus.io/docs/markdown-features#front-matter) to add metadata to your markdown file.
### CI/CD
## CI/CD
- The `master` branch is automatically deployed to the production server (e.g., logos.co) through [CI](https://ci.infra.status.im)
- The `develop` branch is automatically deployed to the staging server (e.g., dev.logos.co) through [CI](https://ci.infra.status.im)
- [CI builds](https://ci.infra.status.im/job/website/job/vac.dev/) `master` and pushes to `deploy-master` branch, which is hosted at <https://vac.dev//>.
- [CI builds](https://ci.infra.status.im/job/website/job/dev.vac.dev/) `develop` and pushes to `deploy-develop` branch, which is hosted at <https://dev.vac.dev//>.
The hosting is done using [Caddy server with Git plugin for handling GitHub webhooks](https://github.com/status-im/infra-misc/blob/master/ansible/roles/caddy-git).
Information about deployed build can be also found in `/build.json` available on the website.
### Change Process