Currently Truffle Teams supports deployments to Ethereum testnets, Ethereum Mainnet, and sandboxes with support for more target networks over time.
Creating a deployment slightly differs depending on which view you have selected for thepage. The general process is as follows:
- Choose a commit to deploy
- Select network and connect wallet
- Select a deployment context
- Start deployment
- Finalize deployment
To begin a deployment, presson the build you'd like to deploy. You can also click . The deployment wizard modal will pop-up and walk you through the deployment process.
For the TABLE view, you'll select a build to deploy from within the deployment wizard. To start a deployment, click, this will open the deployment wizard modal. From the Build to Deploy dropdown, select which build to deploy.
Within the deployment wizard, select a Destination Network, if your wallet has already been setup you can move on to the Select a deployment context step. If your wallet has not been setup, you'll be able to see and click on the button.
MetaMask will pop up asking you to login (if you haven't already). Then you will need to press Connect to confirm the connection with Truffle Teams.
If the wizard hasn't changed (i.e. you don't see a button to start deploying), you likely need to switch your MetaMask network to the destination network. This may reload the page; if this happens, you'll need to repeat the steps above.
Before moving on, make sure you have the correct account selected in MetaMask.
Now you should see the wizard prompting for a Deployment Context. Leave it set to Create a New Deployment, or selet a previous deployment to migrate against.
Deployment Context: This option will let you select an existing deployment on the same network that you'd like to use the deployed artifacts for. Truffle supports the concept of migrating your application and will only run the new migration scripts from the last deployment (a.k.a. the deployment context). This becomes useful in a handful of scenarios: maybe you added an extra contract to work with your existing deployment, your Truffle project uses proxy contracts to upgrade your contracts, and more. Technically speaking, selecting the Deployment Context will put the Truffle artifacts from the deployment context you selected in the directory before running `truffle migrate`.
Now you should be able to see and click onto begin your deployment!
Be Aware: From here on, it's important that you don't close the tab, refresh the page, or lose network connection. We're working on a more robust experience that will enable you to pick up unfinished deployments, but for now our current version requires the tab to stay open and connected.
Truffle Teams will only process so many deployments at the same time, so you may see that your deployment has been queued. You'll have to wait (without closing/refreshing the tab) for your deployment to get to the front of the list. However, we're working diligently to make this experience more seamless going forward.
Once your deployment has started processing, you'll see a list of steps Truffle Teams is doing to prepare for your deployment.
Once the preparation steps are complete, you'll see a screen with a list of your migrations being processed. You should also get a pop-up from MetaMask for your first transaction.
You'll notice that this interface with MetaMask is like sending a transaction to any other dapp. It's your account that is sending this transaction, and you have complete control of it. Additionally, we highly recommend that you change the GAS FEE to be higher so that your transactions run quicker. For testnets like Ropsten, it's affordable to always select the Fast option.
Once you're happy with the transaction gas fee, press Confirm to send your transaction. Once the transaction is confirmed (the timing of confirmations from MetaMask and Truffle Teams may be slightly offset), you'll receive the next transaction. Repeat this process until you see a message that your deployment is being finalized.
After a short wait, you'll see a window with your deployment results:
Your contracts are deployed! That was easy. Go ahead and push Deployment details section of our documentation.or the X in the wizard. If you're using the CARDS view, you should now see a new card under the Staging column. If you're using the TABLE view, the new deployment will appear in the first row. For more information check out the