arcblock/forge-release repository overview

⁠Forge Release

Build forge framework on travis-ci. Currently we do daily releases.

⁠versions

Here's an example versions file

vendors/forge master
vendors/forge-simulator v0.21.0
vendors/forge-starter b6f39dac01fac617379fae9b1a4fd793739a1703
vendors/forge-web master
vendors/forge-workshop v0.5.0
forge-desktop master

Each line consists of two fields, seperated by space

• repo
• branch, tag or commit SHA

Run make submodule-update to checkout the target repo to the specific git reference.

Note: when changing tags in versions file, make submodule-update MUST BE run to make git submodule tag to be updated.

⁠Workflow

forge-release use travis ci to build release for centos and mac osx(darwin). Here's the workflow:

1. prepare the os environment
   • centos: docker image tchen/centos-elixir
   • darwin: travis osx image
2. build the release
   • download the pre-compiled deps from mix-forge-deps repo
   • run make $(TARGET) in each repo in vendors
3. upload the release
   • upload tarballs to github releases
   • upload tarballs to s3 bucket

⁠Adding new vendors

To add new repo under vendors, just do

$ git submodule add [email protected]:ArcBlock/new-repo.git vendors/new-repo

⁠Build c dependency

Please follow the guide in here⁠ for building c dependency.