AWS 2-2: Remove Travis-CI, Switch to GitHub Actions

[rajadain]

Travis-CI.org has been suspended since June 2021: https://travis-ci.org/WikiWatershed/mmw-geoprocessing

Switch to GitHub Actions for CI and deployment.

[JN-Hernandez]

WorkPlan

Summary

Travis-CI.org has been suspended since June 2021, and as such, the mmw-geoprocessing CI/CD pipeline needs to be migrated over to GitHub Actions instead. This work is to track the migration. Ideally, the process should run as follows:

CI:

• Compile scala, only pushing up if successful
  • Running ./scripts/update
• Run ./scripts/test only on a merge to develop
• Integrate automation with a Git Flow release process

PRs:

• Compile scala, only pushing up if successful
• Run ./scripts/test

Release:

• Compile scala, only pushing up if successful
• Run ./scripts/test
• Run ./scripts/cibuild
• Integrate with the GitHub Release process

Steps

• [x] 1. Review the existing .travis.yml file to determine existing scope of CI/CD

• [x] 2. Create a new GitHub workflow, following the outline described within the Summary

  • Addressed in PR #116

[!Note] Integration of the Git Flow release process will not be covered in this first pass.

• [ ] 3. Remove the existing .travis.yml file

• [ ] 4. Integrate the workflow into the Git Flow Release process

  • Addressed in PR #

Criteria for Success

• [ ] 1. The new GitHub workflow works as intended, yielding a successful build run
• [ ] 2. The Travis CI workflow has been retired

Risk

Low

1. This change is low risk, as the Travis CI has already been retired

Rollback

1. N/A - the Travis CI has already been retired and we will not go back to it

Additional Details

Any additional details