You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we perform a handful of caching steps between both the build and testing flows in Bitrise. Over the past year, we've been observing a steady stream of failed runs as a result of cache misses or sometimes sporadic behavior. While caching does save us some time for our builds, the time trade-off has been canceled out by the need to support or react whenever e2e failures occur. The purpose of this ticket is to completely remove all caching steps for now and to follow up with tasks to slowly reintroduce cache steps incrementally and to monitor the behavior over a period of time to ensure stability. To contain the scope, we will only focus on removing cache steps for pr_smoke_e2e_pipeline
Scenario
No response
Design
No response
Technical Details
Remove all cache steps that is used in the pr_smoke_e2e_pipeline
Ensure tests are still running without cache steps
Note the diff in run duration relative to main
Threat Modeling Framework
No response
Acceptance Criteria
All cache steps should be removed in pr_smoke_e2e_pipeline
Tests in pr_smoke_e2e_pipeline should be successful with the exception of failing tests on main (non related to this task)
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
The text was updated successfully, but these errors were encountered:
What is this about?
Currently, we perform a handful of caching steps between both the build and testing flows in Bitrise. Over the past year, we've been observing a steady stream of failed runs as a result of cache misses or sometimes sporadic behavior. While caching does save us some time for our builds, the time trade-off has been canceled out by the need to support or react whenever e2e failures occur. The purpose of this ticket is to completely remove all caching steps for now and to follow up with tasks to slowly reintroduce cache steps incrementally and to monitor the behavior over a period of time to ensure stability. To contain the scope, we will only focus on removing cache steps for
pr_smoke_e2e_pipeline
Scenario
No response
Design
No response
Technical Details
pr_smoke_e2e_pipeline
Threat Modeling Framework
No response
Acceptance Criteria
pr_smoke_e2e_pipeline
pr_smoke_e2e_pipeline
should be successful with the exception of failing tests on main (non related to this task)Stakeholder review needed before the work gets merged
References
No response
The text was updated successfully, but these errors were encountered: