You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently all tests are executed locally inside the docker with help of kind (kubernetes indocker). While it gives pretty much everything we need at the moment - it limits us from using cloud CI solutions like CircleCI, that even has a docker support runs the containers in a separate isolated environment that is impossible to reach with kubectl.
Alternative solution is to host of cluster. Hosting is a subject for discussion, but less expensive is DigitalOcean, where all we need in single droplet with 1gb of RAM, no LB or large volumes. So monthly costs will be a little bit more then $5/month.
In fact when DigitalOcean will update their doctl we will be able to spawn clusters withing console and tear them down when no longer needed. That will let us have very low costs of running.
Free CircleCI account that will trigger the builds. Few minutes of cluster time per tests and that is it.
CircleCI can also be used for continuous delivery. That is actually what FBL already uses. Git tag triggers the tests and if they pass - deployment to npm.
The text was updated successfully, but these errors were encountered:
Currently all tests are executed locally inside the docker with help of kind (
k
ubernetesin
d
ocker). While it gives pretty much everything we need at the moment - it limits us from using cloud CI solutions like CircleCI, that even has a docker support runs the containers in a separate isolated environment that is impossible to reach with kubectl.Alternative solution is to host of cluster. Hosting is a subject for discussion, but less expensive is DigitalOcean, where all we need in single droplet with 1gb of RAM, no LB or large volumes. So monthly costs will be a little bit more then $5/month.
In fact when DigitalOcean will update their doctl we will be able to spawn clusters withing console and tear them down when no longer needed. That will let us have very low costs of running.
Free CircleCI account that will trigger the builds. Few minutes of cluster time per tests and that is it.
CircleCI can also be used for continuous delivery. That is actually what FBL already uses. Git tag triggers the tests and if they pass - deployment to npm.
The text was updated successfully, but these errors were encountered: