Description
What is this about?
We historically used CircleCI as our CI/CD platform. GitHub Actions was introduced much later, in 2018, but we started using it for some of our workflows due to its seamless integration with GitHub repositories. GitHub Actions is also more cost-effective, especially for open-source projects, as it offers free minutes.
We are now at a point where we have partially migrated our workflows from CircleCI to GitHub Actions, but not all of them. This introduces complexity for contributors and blocks us from certain tasks, as data (artifacts) cannot be shared between workflows running in CircleCI and those running in GitHub Actions.
Finalizing the migration to GitHub Actions would allow us to have a unified CI/CD platform, reduce our CI costs, and make it easier to set up and manage workflows in our repository.
First 2 months
- Phase 1 - Reduced Costs
- Phase 2 - Production generation & upload
Last Month
- Phase 3 - Release workflow
Scenario
No response
Design
No response
Technical Details
No response
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
- Engineering (needed in most cases)
- Design
- Product
- QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- Security
- Legal
- Marketing
- Management (please specify)
- Other (please specify)
References
No response