... | ... | @@ -15,4 +15,7 @@ |
|
|
* `HIVEMIND_SOURCE_HIVED_URL` url of a `hived` node providing blocks and virtual operations during syncing i.e.: `{"default":"http://hive-4:8091"}`
|
|
|
* `HIVEMIND_HTTP_PORT` basic port of hive-server process (to be started after successfull sync). This number can be modified by CI system by adding a value of `$CI_CONCURRENT_ID` variable if few concurrent jobs were running. Job description prints a actual port the started hivemind instance is listening to. Also dedicated entry to the created environment is created (including name of branch being deployed to such instance)
|
|
|
|
|
|
|
|
|
\ No newline at end of file |
|
|
1. Planned workflows
|
|
|
1. Regular smoketest. Automatically spawned for each MR created. Required to pass to continue MR processing
|
|
|
1. Partial (incremental) deployment scenarios - after 1st pass of (at least) data-supply phase, it shall be possible to manually trigger only build, deployment and e2e-test phases. This way each developer fixing bugs in API implementations can easily start own working instance on CI server without a need to setup own environment and waiting for `hive sync` process
|
|
|
1. Other deployment scenarios shall be possible for specified number of blocks and hived source node url. Similar scheme could be used for staging and production deployments to be done at Gitlab level. |
|
|
\ No newline at end of file |