-
Notifications
You must be signed in to change notification settings - Fork 18
Migrate CI to GH actions #297
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
Conversation
7015023 to
e3dc711
Compare
dustinbyrne
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything's been re-keyed and should be good to go. See the comments above before merging.
|
|
e3dc711 to
a8badfe
Compare
|
@dustinbyrne I've made these changes — can you merge? I cannot because gh is still waiting for travis — I think you need to disable this in the project settings. |
|
🎉 This PR is included in version 1.27.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This pull request includes significant changes to the CI/CD pipeline and test setup. The primary focus is on migrating from Travis CI to GitHub Actions and improving the test environment configuration.
Required secrets
Note for release to work, some secrets need to be configured in Github Actions (see CI-README.md for details).
CI/CD Pipeline Migration and Improvements:
.github/workflows/build-and-test.yml: Added a new GitHub Actions workflow to handle building, testing, and releasing the project. This workflow includes jobs for building and checking the code, running the test suite across multiple Java versions, and handling releases..github/workflows/build.yml: Removed the existing GitHub Actions workflow for building the project, which included a matrix strategy for testing across different operating systems and Java versions..travis.yml: Removed the Travis CI configuration file, which included setup steps and jobs for testing the project with different JDK versions and handling deployments.Test Environment Configuration:
agent/test/helper.bash: Enhanced the helper script to exportJAVA_HOMEif not already set, load BATS libraries if available, and handle logging more gracefully. [1] [2] [3] [4]agent/test/access/access.bats,agent/test/agent_cli/agent_cli.bats,agent/test/classloading/classloading.bats,agent/test/event/event.bats,agent/test/http_client/httpclient/httpclient.bats,agent/test/http_client/setup_suite.bash,agent/test/http_client/springboot/springboot.bats,agent/test/httpcore/httpcore.bats,agent/test/intellij/intellij.bats,agent/test/jdbc/jdbc.bats,agent/test/petclinic-fw/petclinic-fw.bats: Removed the loading of BATS support and assert libraries, as they are now handled by the helper script. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]Build Configuration Updates:
agent/test/http_client/httpclient/build.gradle,agent/test/httpcore/build.gradle,agent/test/jdbc/build.gradle: Updated the build scripts to fetch theappmapJarandannotationJarfrom environment variables instead of using file trees. [1] [2] [3]Miscellaneous Changes:
agent/test/agent-cli/.gitignore: Removed thespring-petclinicentry.agent/test/bashunit-compat.sh: Removed the file containing helper functions for bashunit scripts.These changes streamline the CI/CD process, improve the test setup, and ensure consistency across different environments.