truebitfoundation / devops Goto Github PK

Tasks:

• Unify all the different community documentation in the same place (Markdown, Wiki, docs website)
• Prepare a top-down approach starting from protocol high level, components, architecture, etc.
• Remove all the old information
• Test in a clean environment all the install commands
• Links to additional information

All the integration tests are running in the CI environment CI when a user raises a PR to be merged in any of the branches.

Depends: #3 and #5

The main intention of this is to protect against accidental push to master.

Automated execution of integration tests between the different components of the stack

The release of new Truebit versions of the software can be triggered using Github tags. The tagging of a new version must start the Continuous Integration (Travis) process of compiling, packaging and releasing the software.

Code can't be merged if UT, IT or code analysis is not good

Depends: #6 & #7

Increase the test coverage of the core components to a number between 70% and 100% depending on the criticality

Tasks:

• Identify the different pieces of code and languages to analyze (Solidity, Rust, Javascript, ..)
• Identify the best tool supporting those languages
• Integrating the code analysis tool selected as part of the continuous integration flow

It would be recommended to have a common template for README files including:

• Truebit banner
• Project Badges (code quality, gitter, travis, ...)
• Table of Contents
• High Level description
• Get Started
• Details
• License

This one could be used as reference: https://github.com/oceanprotocol/keeper-contracts/

Automate the packaging of the application in Docker containers and publishing them in Docker Hub when a new release is published (tagged)

Depends: #3