- Go to https://ci.openmina.com/
- Log in using your GitHub credentials (You can skip the Drone registration by submitting an empty form)
- Navigate to the openmina/mina repository
- Click on NEW BUILD button in the top right corner
- Into the Branch field, type in
openmina-berkeley. This needs to be set to the branch that includes all modified helm charts and our .drone.yml file, which is the configuration file for the CI builds. - (Optional) You can specify parameters (see bellow) as key-value pairs to customize the build
- Click on Create.
If you do not specify any additional Parameters, the build will run with its default parameters.
Available parameters:
| Parameter | Description | Default value |
|---|---|---|
| MINA_REPO | Link to the mina repository | https://github.com/openmina/mina |
| MINA_BRANCH | The branch to create the mina image from | openmina-berkeley |
| NAMESPACE | The namespace to deploy our network to | testnet-default |
Notes:
-
For now, in the
Branchfield, you have to specifyopenmina-berkeley, i.e. the branch we have all our modified helm charts in. To pick a branch to build the image from, you have to specifyMINA_BRANCH. If you want to build from a branch that is in a different repository (e.x.: MinaProtocol/mina), you have to specify two parametersMINA_REPOandMINA_BRANCH. -
The namespace has to be prepared beforehand to include all the resources (like secrets). Currently, we have only one namespace available:
testnet-default.
- Seed nodes: 1
- Plain nodes: 8
- Producer nodes: 5
- Snark worker nodes: 64
You can check out the configuration in the helm charts at: https://github.com/openmina/mina/blob/openmina-berkeley/helm/openmina-config/values/common.yaml