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

Move the build from Travis to GitHub Actions #343

Open
4 tasks
cxbrooks opened this issue May 12, 2022 · 0 comments
Open
4 tasks

Move the build from Travis to GitHub Actions #343

cxbrooks opened this issue May 12, 2022 · 0 comments

Comments

@cxbrooks
Copy link
Member

I got a start on setting up GitHub actions and have something that configures and runs ant, see https://github.com/icyphy/ptII/blob/cxbrooks-github-actions-1/.github/workflows/github-actions-ptII.yml

The devil is in the details. To run all the tests, there is quite a bit of configuration of optional packages that needs to be done. The Travis build is split up in to a bunch of different subsets of the tests that generate xml and then a final step collates all the xml and generates https://www.icyphy.org/ptII-test/reports/junit/html/index.html

As far as moving to GitHub actions, there are these components:

  • Run the tests and update the gh-pages branch with the results
  • Install the optional components, which are currently done in ptII/.travis.yml. We could create a separate script
  • Figure out how to cache and use files generated by GitHub actions. For example, the javadoc output and OpenCV.
  • If necessary, figure out how to run GitHub actions jobs longer than 6 hours.
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