Difficulties integrating Taiko scripts with continuous integration (CI) pipelines.
cryptorylai opened this issue · comments
Problem: Many of the users face challenges whilst trying to integrate Taiko scripts seamlessly into their CI pipelines, main to inefficiencies within the test workflow and hindering automation efforts.
Solution: Develop a complete manual in the Taiko documentation that outlines pleasant practices for integrating Taiko scripts with popular CI equipment including Jenkins, Travis CI, or GitHub Actions. Provide targeted instructions, pattern configuration files, and troubleshooting suggestions to facilitate easy integration and make certain reliable execution of Taiko exams inside CI environments.
Things are still being built and team is taking all the feedback into consideration. With the launch of Mainnet, everything will be fine, fingers crossed
Yes this remains true and I'm still yet to find any resources that address it. Indeed integration with either Travis CI or Github Actions would be great as there is a large user pool that specialize in either
@cryptorylai i don't understand the use case for simple-taiko-node being used in CICD. can you explain the specifics about your use case and desired feature request(s)? Otherwise we will close this issue, thanks.
Closed due to inactive.