Description

zos, when it is updating its on-chain versions of the contract, commits all the details of where the new code is to zos.staging.json and zos.production.json. This happens while we are in the deploy step of run_tests and consequently when we are running tests in either staging or production environment from docker. We need any changes here to back propagate into the repository in a fully automated way. This likely means that the triggers will fire again and re-run the tests, but the next time around there will be no updates to the contracts on the chain. Here is what needs to happen.

PR must contain

• a first commit title that starts with 'CRUCIBLE-N:'
• vaults for production and staging will need to contain creds for a github user that can commit to only dev and master branches.
• when a change is made after the zos update call, we need to commit that change.

Example PR

#2

Bounty

None

Description

We need an easier way to version bump. Add a script that does that.

PR must contain

• a first commit title that starts with 'CRUCIBLE-N:'
• code
• tests

Example PR

#2

Bounty

None

Description

We need a way to both get the index of a crucible in the crucibles list (Foundry.getIndexOf()), and then delete that crucible based on its index and address (Foundry.deleteCrucible()).

PR must contain

• a first commit title that starts with 'CRUCIBLE-1:'
• code
• tests

Example PR

#1

Bounty

None

Description

Fix the race condition that appears on the kovan testnet or with infrua that fires off the event that a contract has been created from the foundry, but the contract has no code yet. This could be due to server pooling on infura mixed with kovan slower block times. Either way, it's a good chaos monkey, and should be resolved.

Also, version bump to 1.0.14 for what should be the first fully successful auto deploy.

PR must contain

• a first commit title that starts with 'CRUCIBLE-N:'
• code
• tests

Example PR

#2

Bounty

None

Description

Anyone that is going to test against our contracts on tests nets needs our contracts to be on all the tests nets. This means we need to add ropsten and kovan testnets to the staging deploy.

PR must contain

• a first commit title that starts with 'CRUCIBLE-N:'
• code
• tests

Example PR

#2

Bounty

None

Description

Because the code is setup to use a pool of servers, we often get a nonce too low error when running tests or deploying. My original fix was to catch this error, but then I realized it happens from other tools. The better solution is to fix the nonce provider for the engine. Do this and fix the problem.

PR must contain

• a first commit title that starts with 'CRUCIBLE-N:'
• code
• tests

Example PR

#2

Bounty

None

Description

Test the entire pipeline with a version bump to 1.0.3.

PR must contain

• a first commit title that starts with 'CRUCIBLE-N:'
• code
• tests

Example PR

#2

Bounty

None

Description

The old setup of our wallet/provider/engine in truffle.js was a complete mess. Refactor to make it cleaner.

PR must contain

• a first commit title that starts with 'CRUCIBLE-N:'
• code
• tests

Example PR

#2

Bounty

None

Description

Create the production deploy pipeline.

PR must contain

• a first commit title that starts with 'CRUCIBLE-N:'
• code
• tests

Example PR

#2

Bounty

None

Description

It's a redundant and dangerous waste of time to wait for unit tests to run on a production deploy.

PR must contain

• a first commit title that starts with 'CRUCIBLE-N:'
• code
• tests

Example PR

#2

Bounty

None