This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
Circle: Tenderly Integration #536
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
March 19, 2020 15:39
We can by-pass running tenderly init on every circle run by setting up this basic tenderly config file.
Here we integrate tenderly push to the migration script. We need to do this from the utility box because that's where the truffle context and contracts live. We could probably try this in a separate Circle job after the contract copyback, but I want to try with as few moving bits as possible first.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Intro
On contract migration in Circle we're using the Tenderly CLI to push the newly deployed contracts to our Tenderly dashboard. This lets the folks at Tenderly associate transactions from our private networks, or ropsten with contracts and offer all the sweet insights they do.
What We Did
Circle Context / Access
A new Circle Context for
TENDERLY_TOKEN. This is used with thetenderly loginstep and is required before we can push contracts. We've addedhemidall@thesis.coto our Tenderly dashboard and are using the token for that account for Circle migrations. This token as push only access to the dashboard. Login info for Heimdalls account on Tenderly is in 1Password.circleci-migrate-contracts.shWe've added an additional step post contract migration that does
tenderly loginandtenderly push. You can see the output of our initial test on this job. If you're already logged in the login step doesn't fail, it just continues to push.utility-box
Installed Tenderly via curl instructions here. There will be a follow up PR to integrate this install with utility-box setup, on the Terraform side. That should not block merging here though, I've manually installed the tool for now in both keep-dev and keep-test.