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

Reintroduce working CI tests to GitHub Actions #311

Open
engn33r opened this issue Apr 21, 2021 · 0 comments
Open

Reintroduce working CI tests to GitHub Actions #311

engn33r opened this issue Apr 21, 2021 · 0 comments

Comments

@engn33r
Copy link
Contributor

engn33r commented Apr 21, 2021

To continue the discussion from PR #309, the transition from TravisCI to GitHub Actions wasn't able to get the Makefile tests or Docker integration tests running properly. This could be from a lack of knowledge on my side, but there is probably an improved approach to these tests than what is in the older TravisCI flow. To move towards a fix, we should determine:

  1. What did the Docker integration tests do?
  2. What did the Makefile tests do?
  3. What would be the best approach to getting the same results for these tests now that Go modules exist?
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

1 participant