Also note that on the OUSD side we use hardhat. See deploy scripts.
At a minimum we should standardize and use a single deployment tool per repo.
In terms of requirements, it would be good to have a way to keep track of the history of deploys. Either by using a naming convention for scripts or by leveraging the framework if it supports that natively.
We have have been using 2 different tools for deploying contracts:
Also note that on the OUSD side we use hardhat. See deploy scripts.
At a minimum we should standardize and use a single deployment tool per repo. In terms of requirements, it would be good to have a way to keep track of the history of deploys. Either by using a naming convention for scripts or by leveraging the framework if it supports that natively.