development

Last updated: 2025-04-02 09:04:20.181376 File source: link on GitLab

Purpose and audience

The development environment is composed of a somewhat larger (than feature) network of heterogeneous devices sourced from the community. Since NuNet, as a decentralized network, will not have control of the devices sourced from community, the development environment will encompass communication channels with the community members who will participate in the NuNet testers program.

CI/CD stages

Branch: develop branch

Develop environment is used to run the following CI/CD pipeline stages according to the pre-defined schedule, to be communicated to community testers:

• static analysis;

• unit tests;

• static security tests;

• build (if needed by the feature);

• functional tests / API tests (if needed by the feature);

• security tests

• automatic regression tests

Architecture

The development environment contains:

• virtual machines and containers hosted in NuNet cloud servers;

• machines owned by NuNet team members;

• machines provided by the community members on constant basis via NuNet Network private testers program;

Triggering schedule

The CI/CD pipeline in development environment is triggered in two cases:

1. automatically when a merge request is approved and merged into the developbranch (see all merged;

2. according to the pre-determined schedule for running stages that are more heavy on compute requirements -- which ideally may include the more advanced stages ; depending on the speed of development, NuNet may be schedule weekly or nightly builds and runs of the platform with the full pipeline (possibly including the latest stages of the CI/CD pipeline normally reserved for Staging environment only). In principle, Development environment should be able to run all automatic tests.