Fixes #4553 : Migrate CI/CD Pipeline from TravisCI to GitHub Actions
This PR adds github ci/cd workflows to existing TravisCI configuration, maintaining all existing pipeline functionality.
The new GitHub Actions workflow includes:
- Code linting with flake8
- Docker build process
- Frontend testing with Karma
- Backend testing with pytest and coverage reporting
- Automatic deployment on master branch merges
Required secrets:
-
DOCKER_USERNAME- Docker registry username -
DOCKER_PASSWORD- Docker registry password -
COVERALLS_REPO_TOKEN- Token for Coveralls coverage reporting -
SSH_PRIVATE_KEY- Deployment SSH key
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 69.53%. Comparing base (
96968d6) to head (9cc2a08). Report is 1151 commits behind head on master.
Additional details and impacted files
@@ Coverage Diff @@
## master #4576 +/- ##
==========================================
- Coverage 72.93% 69.53% -3.40%
==========================================
Files 83 20 -63
Lines 5368 3591 -1777
==========================================
- Hits 3915 2497 -1418
+ Misses 1453 1094 -359
see 65 files with indirect coverage changes
see 65 files with indirect coverage changes
Continue to review full report in Codecov by Sentry.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update 8ae26ff...9cc2a08. Read the comment docs.
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
- :package: JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
Hi @lazyperson1020 , Can you please update your script with the latest travis.yml in the repo?
@RishabhJain2018 I have made some changes
@RishabhJain2018 any update on this sir?
The CI/CD migration file looks good. However, I would suggest adding Docker layer caching to speed up builds and uploading test and coverage reports as artifacts. Would this be a valid approach, and would it be okay if I work on these improvements? @RishabhJain2018 @lazyperson1020
I will try that @wahid18-maqs