-
Notifications
You must be signed in to change notification settings - Fork 35
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
jenkins ci to github actions #114
Conversation
.github/workflows/ci.yml
Outdated
- name: Validate composer.json and composer.lock | ||
run: | | ||
sudo composer self-update | ||
- name: Cache Composer packages |
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.
I do not think we need cache. Based on https://github.com/actions/cache?tab=readme-ov-file#cache-limits, caches that are not accessed within the last week will be evicted. Consider the frequency of the changes in this repo, the cache will most likely be evicted. Also, the build is pretty fast. I do not see the benefit of cache.
lgtm |
Purpose
Jenkinc CI to GH actions
Summary
Jenkinc CI to GH actions
Testing
Testing integration tests
https://github.com/SiftScience/sift-php/actions/runs/9605537571/job/26493378684
only buids
https://github.com/SiftScience/sift-php/actions/runs/9605562465
Checklist