Migration from CircleCI to GitHub Actions - Flask MV2 Build

[itsyoboieltr]

What is this about?

This ticket covers the effort required to migrate our continuous integration and deployment processes from CircleCI to GitHub Actions. The migration in this ticket involves:

• Evaluate the current CircleCI workflows and identify the equivalent configurations in GitHub Actions.
• Create and configure GitHub Actions workflows to replicate the existing CircleCI pipelines.
• Thoroughly test the new GitHub Actions workflows to ensure they function as expected and meet our CI/CD requirements.
• Gradually phase out CircleCI once the GitHub Actions workflows are fully operational and stable.

Flask MV2 Build

• prep-build-flask-mv2
  • validate-source-maps-flask-mv2
  • test-e2e-chrome-rpc
  • test-mozilla-lint-flask-mv2

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