Skip to content
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

3021: Reduce CI runtime #3022

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

3021: Reduce CI runtime #3022

wants to merge 2 commits into from

Conversation

steffenkleinle
Copy link
Member

@steffenkleinle steffenkleinle commented Dec 5, 2024

Short description

Reduce CI runtime by removing browserstack upload and e2e tests from commits on main and web e2e tests from normal commits.

Proposed changes

  • Add native_browserstack workflow to manually deliver android and ios to browserstack
  • Remove browserstack upload from commit_main
  • Remove automatic runs of e2e_tests for commits on main (-> e2e tests are only run before deliveries)
  • Remove e2e_web from commit workflow
  • Remove build_ig_test_cms_web where not necessary (not needed for web e2e tests)
  • Update docs

Side effects

  • e2e tests are not run automatically for commits on main and should be triggered manually if necessary (still running for deliveries though)
  • native builds are not uploaded to browerstack automatically anymore (can be triggered manually using new native_browserstack workflow

Testing

None, just have a look at the CI.

Resolved issues

Fixes: #3021

Additonal context

image
image


… from commits on main and web e2e tests from normal commits
Copy link
Contributor

@LeandraH LeandraH left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! It's really wonderful to see this number!
image

Just to clarify, the delivery workflow delivers web and native to beta, and to get from beta to production, we need to start web_production_delivery and native_production_delivery separately, correct?

@steffenkleinle
Copy link
Member Author

Looks great! It's really wonderful to see this number! image

Just to clarify, the delivery workflow delivers web and native to beta, and to get from beta to production, we need to start web_production_delivery and native_production_delivery separately, correct?

Nope, for this the promotion workflow is for :) web and native production delivery workflows directly deliver a new version to production without beta testing in between

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Reduce CI runtime
2 participants