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

CI/CD #146

Open
gaboesquivel opened this issue Oct 22, 2018 · 2 comments
Open

CI/CD #146

gaboesquivel opened this issue Oct 22, 2018 · 2 comments

Comments

@gaboesquivel
Copy link
Contributor

gaboesquivel commented Oct 22, 2018

I want to start working on the CI/CD configuration.

Let's use this threat for discussion.

I thinking on using the following setup.

  • Travis CI would run lint and test commands on for every PR and commit.
  • Netlify would create an ephimeral version of the frontend for every PR, that could be connected to the Jungle.
    • Problem is if you want to update the contracts, then we would need to think on a strategy for the ephemeral dapp to use those contracts. I think we can start without this and figure this out later.
  • Travis will run automated test with docker compose.

Please share your thoughts.

@leordev
Copy link
Member

leordev commented Oct 22, 2018

That's a nice start! You totally have my greenlight to go with above! 😄

@gaboesquivel
Copy link
Contributor Author

Cool. For ephemeral contract testing environments, we could spin up a nodes with those contract changes on a cloud and build the react client with the right config to connect to those nodes. I have experience with AWS, ECS, Docker. We can use any service, the one that does the job better and less cumbersome.

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

No branches or pull requests

2 participants