Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sharing binary on test using mutl-stage build and cache #1721

Open
foriequal0 opened this issue Jul 29, 2019 · 1 comment
Open

Sharing binary on test using mutl-stage build and cache #1721

foriequal0 opened this issue Jul 29, 2019 · 1 comment

Comments

@foriequal0
Copy link
Contributor

foriequal0 commented Jul 29, 2019

We build CodeChain binary in every task in Travis. It takes about 10-15 mins per task.

  1. To run clippy and rustfmt
  2. To make sure it doesn't have a compile error.
  3. Unit tests and E2E tests.
  4. Dynamic validator tests 1
  5. Dynamic validator tests 2.

We at least use a build output from 3 in 4, 5.
We might reuse a build cache from 2 in 3. When many features in clippy and rustfmt are stabilized, we also reuse the cache from 1 in 2.

@foriequal0 foriequal0 self-assigned this Jul 29, 2019
@kseo kseo added the test label Sep 20, 2019
@kseo kseo added the build label Oct 4, 2019
@foriequal0
Copy link
Contributor Author

We can do this relatively easily on Github Actions with artifacts than Travis CI.
https://help.github.com/en/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts
Describing task dependency in Github Actions is also easier than Travis CI.
https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants