Environments allow control of the continuous deployment of your software within Superblocks.

It’s important to know that:

  • Environments are like tags for your CI jobs, describing where code gets deployed.
  • Deployments are created when jobs deploy versions of code to environments, so every environment can have one or more deployments.


  • Provides a full history of your deployments for each environment.
  • Keeps track of your deployments, so you always know what is currently being deployed on your servers or the blockchain.

Environment using our Web3 Providers

In order to make life easier, we have embedded the feature of automatically creating an environment for you when you are performing a deployment using one of our custom Web3 Providers.

For example, when you setup your provider like this, we will perform a set of actions:

rinkebyMetamaskProvider = new ManualSignProvider({ 
    projectId: '{project_id}',
    token: '{token}',,
    from: '{your_address}', 
    endpoint: 'https://rinkeby.infura.io/v3/{your_api_code}',
    networkId: '4'
  1. The networkId represents in this case a given environment.
  2. If the networkId is a well known (Rinkeby, Ropsten, Mainnet, etc), we will automatically convert the id to the well known name to make it easier to identify in the dashboard
  3. When creating the deployment, we will automatically create the environment if it does not exists or link the deployment to a known one.
  4. We will give you a comprehensive view in the dashboard to track the deployment to any given network you have deployed to.

When you are on the deployments page, you can see the full list of deployments performed in that particular project in the past.

Environment Details