Need your feedback for research on evaluating automated conversion from Travis CI to GitHub Actions workflows

[nhossaincse]

I am doing research on evaluating automated conversion of CI configurations from Travis CI to GitHub Actions. As part of this study, a GitHub Actions workflow has been generated that aims to approximate the existing Travis CI configuration as closely as possible.

In this case, the generated workflow did not complete successfully during our test run, but we are still very interested in understanding how well the translated workflow reflects the structure and intent of your original Travis CI setup. Even if you do not have plans to migrate to GitHub Actions, I would greatly appreciate any feedback you can provide on how well this migrated workflow aligns with the original configuration. You may also give a five-point rating, which would be very helpful for the study.I just added the actions.yml file. Thank you.

[gerhardol]

Some issues:

• git lfs were not handled
• whitespace issues

Java version in build.properties were not updated to Travis, not migrated For some reason Java VM mem settings had to be adjusted

I pushed changes to my branch tmp/agp. That also have other fixes like how to build/lint/test, updated versions

[nhossaincse]

Thank you so much for taking the time to review this @gerhardol. I would sincerely appreciate it if you could provide a rating on a five-point scale, as it would be very helpful for my research.