9 Commits

Author SHA1 Message Date
1abedba9bf
ci: move it to a container
Referenced issue:
* https://github.com/status-im/infra-ci/issues/188
2025-10-23 12:03:42 +02:00
Siddarth Kumar
a65216cc46
ci: wrap nix.develop in script block 2025-07-11 13:44:45 +05:30
Siddarth Kumar
87eaaea091
ci: add nix flake and use in CI
Using system tooling can lead to weird behavior of available Node
versions, for example this IPv6 resolution error:
```
[3/5] Fetching packages...
error Error: connect EHOSTUNREACH 2606:4700::6810:1922:443
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16)
```
2025-07-11 13:38:53 +05:30
58394dec00
feat: use two deploy branches for CI builds
This way we have two branches on GitHub that reflect the state of the
website after CI build has finished and pushed. See README.

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2024-02-20 10:18:26 +01:00
378518a427
ci: improve devel publishing conditional
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2024-02-19 14:50:20 +01:00
37339d204f
ci: add genaration of build.json matadate file
Useful for debugging missing deployments.

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2024-02-19 14:50:19 +01:00
swb
fc28821b62
fix jenkinsfile 2023-06-13 18:56:32 +01:00
swb
22dd4103ab
fix jenkinsfile 2023-06-13 10:37:45 +10:00
swb
217dd7d0cb
add jenkinsfile
In the `Build` stage, the site generated into `build` directory.
Also the `CNAME` file created in the same stage with `PROD_SITE`
2023-03-21 22:24:01 +00:00