This repository has been archived by the owner on Apr 26, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 36
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #381 from status-im/develop
Deploy Week 13 2018
- Loading branch information
Showing
68 changed files
with
2,933 additions
and
847 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
# Clojure CircleCI 2.0 configuration file | ||
# | ||
# Check https://circleci.com/docs/2.0/language-clojure/ for more details | ||
# | ||
version: 2 | ||
jobs: | ||
build: | ||
docker: | ||
# specify the version you desire here | ||
- image: circleci/clojure:lein-2.8.1-browsers | ||
|
||
# Specify service dependencies here if necessary | ||
# CircleCI maintains a library of pre-built images | ||
# documented at https://circleci.com/docs/2.0/circleci-images/ | ||
# - image: circleci/postgres:9.4 | ||
- image: circleci/postgres:9.6 | ||
environment: | ||
- POSTGRES_USER=commiteth | ||
- POSTGRES_DB=commiteth | ||
|
||
working_directory: ~/repo | ||
|
||
environment: | ||
LEIN_ROOT: "true" | ||
# Customize the JVM maximum heap limit | ||
JVM_OPTS: -Xmx3200m | ||
|
||
steps: | ||
- checkout | ||
|
||
# Download and cache dependencies | ||
- restore_cache: | ||
keys: | ||
- v1-dependencies-{{ checksum "project.clj" }} | ||
# fallback to using the latest cache if no exact match is found | ||
- v1-dependencies- | ||
|
||
- run: lein deps | ||
|
||
- save_cache: | ||
paths: | ||
- ~/.m2 | ||
key: v1-dependencies-{{ checksum "project.clj" }} | ||
|
||
- run: echo $ETH_WALLET_JSON > $ETH_WALLET_FILE | ||
|
||
# run tests! | ||
- run: lein test |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -26,4 +26,3 @@ node_modules | |
/config-prod.edn | ||
/config-dev.edn | ||
/config-test.edn | ||
/src/java |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
This document describes process guidelines to be followed when contributing to Status Open Bounty repo. | ||
|
||
First, make sure to familiarize yourself with the [README](https://github.com/status-im/open-bounty/blob/develop/README.md) and [Testing](https://github.com/status-im/open-bounty/blob/develop/doc/testing.md) documents in order to setup the project properly. | ||
|
||
# Issues | ||
- Issues should have type, priority and size (difficulty) assigned via corresponding labels | ||
- Issue descriptions should include the following fields: | ||
- **Summary** | ||
- **Type** | ||
- (*Features or enhancements only*) **User story** | ||
- (*Bugs only*) **Expected behavior** | ||
- (*Bugs only*) **Actual behavior** | ||
- **Additional information** | ||
|
||
# Pull requests | ||
- Branch names should include: | ||
- prefixes indicating issue type (`bug`, `feature`, `doc`, `test`) | ||
- short description in lisp-case | ||
- and include associated issue number | ||
|
||
For instance, `bug/messy-problem-#1234` | ||
- Start the title of the PR with [FIX #NNN], where #NNN is the issue number | ||
- Always include `Status:` in the PR description to indicate whether PR is `WIP` or `Finished`. | ||
- PR description should include the following sections: | ||
- **Summary** | ||
- **Notes** | ||
- **Status** | ||
- Merges into `develop` branch should be approved by at least 1 person, into `master` - by 2. |
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# OpenBounty Contracts | ||
|
||
This directory contains all the underlying smart contracts used by the OpenBounty platform. | ||
|
||
- A script `contracts/build.sh` is part of this repository and can be used to | ||
compile the contracts and copy Java interfaces into `src/java/`. | ||
|
||
In order to run the script the following dependencies have to be met: | ||
|
||
- [solc](#solc) | ||
- [web3j](#web3j) | ||
|
||
### solc | ||
|
||
Solidity compiler [0.4.15](https://github.com/ethereum/solidity/releases/tag/v0.4.15) is required and needs to be in $PATH. | ||
Detailed [installation instructions for various platforms](https://solidity.readthedocs.io/en/develop/installing-solidity.html) can be found in the official Solidity documentation. | ||
|
||
``` | ||
brew install https://raw.githubusercontent.com/ethereum/homebrew-ethereum/de1da16f7972a899fc8dd1f3f04299eced6f4312/solidity.rb | ||
brew pin solidity | ||
``` | ||
|
||
### web3j | ||
|
||
Web3j [2.3.0](https://github.com/web3j/web3j/releases/tag/v2.3.0) is required and the command line tools need to be in $PATH. | ||
Installation instructions for the command line tools can be found in the [Web3j Command Line Tools documentation](https://docs.web3j.io/command_line.html). | ||
|
||
``` | ||
brew install https://raw.githubusercontent.com/web3j/homebrew-web3j/881cf369b551a5f2557bd8fb02fa8b7b970256ca/web3j.rb | ||
brew pin web3j | ||
``` |
File renamed without changes.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
# Table of contents | ||
|
||
- [Testing guide](testing.md) | ||
- [Troubleshooting](cookbook.md) | ||
- [Deployment flow](deployment_flow.md) | ||
- [Development workflow](development_workflow.md) | ||
- [Deployment flow](deployment_flow.md) | ||
- [Payout flow](payout_flow.md) | ||
- [Common sync issues](sync_issues.md) |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# Testing pull requests in Open Bounty | ||
|
||
All new functionality and features both are being delivered by pull requests (hereinafter PRs). | ||
How to test PR? Steps below could help a bit! | ||
|
||
### Prerequisites | ||
Requirements for PRs to be tested: | ||
* should be in `To test` column in `Pipeline For Pull Requests` project | ||
* should be updated to last develop. If button `Update` is avaivable on particular PR, click it and wait until it will be built. | ||
* shouldn't have conflicts with `develop` branch | ||
* should have a successful build in Jenkins [status-openbounty-app](https://jenkins.status.im/job/status-openbounty/job/status-openbounty-app/view/change-requests/) | ||
|
||
|
||
### Deployment | ||
In order to deploy feature to [testing env](https://testing.openbounty.status.im/) you should **rebuild** PR you are about to test (all open PRs are in [Jenkins](https://jenkins.status.im/job/status-openbounty/job/status-openbounty-app/view/change-requests/)). | ||
|
||
When PR is successfully build and deployed, [testing env](https://testing.openbounty.status.im/) with deployed PR is accessible in 2-3 mins. | ||
|
||
Only one at one time PR can be deployed on [testing env](https://testing.openbounty.status.im/) | ||
|
||
Fresh develop branch with last changes is deployed automatically on [staging env](https://openbounty.status.im:444) | ||
|
||
### Testing | ||
1) Move appropriate PR card to IN TESTING on the [Board](https://github.com/status-im/open-bounty/projects/3) and let people know you are on it - assign it to yourself! :) | ||
2) Сheck the functionality current PR fixes / delivers (positive/negative tests related to the feature). In curtain cases it's worth to look in 'Files changed' tab in GitHub to check the list of what was changed to get understanding of the test coverage or "weak" places that have to be covered. Ask PR-author in #openbounty channel in slack what was changed if it's not clear from the notes in PR. | ||
3) Check reasonable regression using [SOB-general test suite](https://ethstatus.testrail.net/index.php?/suites/view/27&group_by=cases:section_id&group_order=asc) | ||
4) No issues? Perfect! Put appropriate label to the PR (`Tested - OK`), merge it to develop (using `Rebase-Merge`) and move the PR instance to `Merged to develop`. | ||
5) Found issues? Check for duplicates before adding one. Hint: make sure the issue is really introduced by current PR - check latest `develop` branch on [staging env](https://openbounty.status.im:444) . Issue exists in develop? Check existing issues list and make sure you are not adding duplicates before creating your own bug :) | ||
**All PR-specific issues should be added as comments to tested PR.** | ||
Once all issues are logged put label `Tested-issues` to the PR and notify developer that there are several problems that are preventing the PR to merge. Move the PR to `Reviewing, waiting for contributor` on the board if PR is developed by external contributor, and to `Developing` - if it is presented by core contributor. | ||
|
Oops, something went wrong.