ci: added pipeline to test colima support on macos
Describe the changes that are made
- Wrote a pipeline to test colima support.
Links & References
Closes: #3119
🔗 Related PRs
- NA
🐞 Related Issues
- #3119
📄 Related Documents
- NA
What type of PR is this? (check all applicable)
- [ ] 📦 Chore
- [ ] 🍕 Feature
- [ ] 🐞 Bug Fix
- [ ] 📝 Documentation Update
- [ ] 🎨 Style
- [ ] 🧑💻 Code Refactor
- [ ] 🔥 Performance Improvements
- [ ] ✅ Test
- [x] 🔁 CI
- [ ] ⏩ Revert
Added e2e test pipeline?
- [ ] 👍 yes
- [x] 🙅 no, because they aren't needed
- [ ] 🙋 no, because I need help
Added comments for hard-to-understand areas?
- [x] 👍 yes
- [ ] 🙅 no, because the code is self-explanatory
Added to documentation?
- [ ] 📜 README.md
- [ ] 📓 Wiki
- [x] 🙅 no documentation needed
Are there any sample code or steps to test the changes?
- [ ] 👍 yes, mentioned below
- [x] 🙅 no, because it is not needed
Self Review done?
- [] ✅ yes
- [x] ❌ no, because I need help
Any relevant screenshots, recordings or logs?
- NA
🧠 Semantics for PR Title & Branch Name
Please ensure your PR title and branch name follow the Keploy semantics:
📌 PR Semantics Guide
📌 Branch Semantics Guide
Examples:
- PR Title:
fix: patch MongoDB document update bug - Branch Name:
feat/#1-login-flow(You may skip mentioning the issue number in the branch name if the change is small and the PR description clearly explains it.)
Additional checklist:
- [x] Have you read the Contributing Guidelines on issues?
- [x] Have you followed the PR Semantics guide for naming this PR?
- [x] Have you followed the Branch Semantics guide for naming your branch?
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅
The CLA check failed. Please ensure you have:
- Signed the CLA by commenting 'I have read the CLA Document and I hereby sign the CLA.'
- Used the correct email address in your commits (matches the one you used to sign the CLA).
After fixing these issues, comment 'recheck' to trigger the workflow again.
I have read the CLA Document and I hereby sign the CLA
recheck
hey how have you tested this?
could you test this on your fork and give me the url of the action run?
Hey @officialasishkumar , I wasn't sure on how to test the action. Thank you for the suggestion, I will do it asap and give you the url. Also there have been few errors which I am now fixing, so should I close this PR and do a new one with the corrected script or is it fine if I do multiple fixing commits in this same PR? Thank you for the help! :)
You can do everything in this PR
@officialasishkumar Hey, I have been trying to fix the pipeline for the past couple of hours, but have been getting errors. This is the action url: https://github.com/nakul-krishnakumar/keploy/actions/runs/18944275108/job/54091070714?pr=1 Could you please verify it and let me know what changes can be made it resolve the error? Also the entire pipeline is taking more than 20 minutes to run. Is that expected or is my entire approach wrong? Please let me know that so I can fix accordingly. Thank you :)
Successfully tested the pipeline here: https://github.com/nakul-krishnakumar/keploy/actions/runs/18965288414/job/54160611528?pr=1, and it finally works as expected. Please review it @officialasishkumar .
will review
Hey @officialasishkumar, I was trying to fix the DCO error and other commits got into this PR. Now this PR says updates 13 files. Please review and let me know what I should do. Should I create a new PR?
Tested the updated workflow with code written in .sh file, it works perfectly, Link: https://github.com/nakul-krishnakumar/keploy/actions/runs/18979485830/job/54208064640?pr=1 Please let me know if I should make a separate PR as in the current PR I can see some other commits that came when I did force push to resolve DCO error. @officialasishkumar
i have updated the branch
i have updated the branch
Thanks, and btw when you asked me to move all code to .sh, did you also mean docker cli commands?
Updated the code to follow project convention. New workflow ran successfully: github.com/nakul-krishnakumar/keploy/actions/runs/19012134057/job/54294646438?pr=1 @officialasishkumar
Will look into it
@officialasishkumar updated the workflow to use samples/gin-mingo . :+1:
@officialasishkumar any updates?
@officialasishkumar any updates on this PR?