Substrate: Make master branch stable by having Continuous integration
Proposing an enhancement and a must have feature from the get go 馃樅
Witnessed instability in master branch due to major feature integration and I believe its the right time to have an automatic test integration pipeline before merging in to master branch.
Either integrate Circle CI or Travis CI with automatic tests.
Kalanamith
All 6 comments
Hey, we already have a CI that tests all our pull requests.
bkchr
on 22 Nov 2018
@bkchr the latest master branch cannot be compiled in MacOS with substrate node template project today. I have seen the CI integration. If it works feel free to close this. Happened for 3 people today with the latest master.
Kalanamith
on 22 Nov 2018
Yeah sorry for that, master is currently evolving really fast. We should pin the template project to a specific commit.
bkchr
on 22 Nov 2018
Cool, if there is a way to integrate a test-net (eg:- node template project ) dependencies. Will be super cool. Thanks 馃憤
Kalanamith
on 22 Nov 2018
@Kalanamith https://github.com/paritytech/substrate-node-template/pull/8 should fix your problems :) This will also pin the example to a specific substrate version, so it should work, even when we break something in master.
bkchr
on 22 Nov 2018
@bkchr Great, Thanks a lot!
Kalanamith
on 22 Nov 2018
Related issues
expenses
路
5Comments
qalqi
路
3Comments
thiolliere
路
3Comments
xlc
路
5Comments
xlc
路
6Comments
Most helpful comment
@Kalanamith https://github.com/paritytech/substrate-node-template/pull/8 should fix your problems :) This will also pin the example to a specific substrate version, so it should work, even when we break something in master.